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 :
- DatabaseJournal: Salesforce Heroku Offers Standalone Cloud-Based PostgreSQL Database — DatabaseJournal.com
- InfoQ: Heroku Launches Postgres as a Standalone Service.
- ZDNet: Heroku launches cloud Postgres database | Cloud | ZDNet UK
- eWeek: Heroku Launches PostgreSQL Database-as-a-Service - Application Development - News & Reviews - eWeek.com
- PCWorld: Salesforce.com’s Heroku Launches Stand-alone Database Service | PCWorld Business Center
- Tools Journal: Heroku Launches PostgreSQL Database As A Service
- CloudBeat: Heroku debuts SQL database-as-a-service for developers | VentureBeat
- SiliconANGLE: Heroku Launches Standalone PostGres Database-as-a-Service | ServicesANGLE
- ReadWriteWeb: Heroku Launches PostgreSQL Standalone Service - ReadWriteCloud
- GigaOm: Heroku launches SQL Database-as-a-Service — Cloud Computing News
- ITProPortal: Heroku Announces PostgreSQL Database-as-a-Service for Developers | ITProPortal.com
Original title and link: Standalone Heroku Postgres’ Unanswered Question (©myNoSQL)
