NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter



Standalone Heroku Postgres’ Unanswered Question

While the offer is clear and valuable in itself:

  • 99.99% uptime
  • 99.999999999% (eleven nines) durability
  • read-only asynchronous replicas
  • database cloning

I’ve been reading all posts about the announcement looking for the answer to the most obvious question: why would you use Heroku’s Postgres service from outside the Heroku platform?

As far as I can tell:

  • the network latency will be significant
  • network partitions will occur (more often than having both you application and data in the same DC)
  • transfer costs will be significant

So what is the answer?

Media coverage :

Original title and link: Standalone Heroku Postgres’ Unanswered Question (NoSQL database©myNoSQL)