DaaS: All content tagged as DaaS in NoSQL databases and polyglot persistence
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)
Google has just announced a new (lab) product: Google Cloud SQL which is Google’s Database-as-a-Service version of Amazon RDS—based on initial information, Google Cloud SQL could be characterized as a very basic/intro version of Amazon RDS.
Main features listed in the announcement:
- Managed environment
- High reliability and availability - your data is replicated synchronously to multiple data centers. Machine, rack and data center failures are handled automatically to minimize end-user impact. It also support asynchronous replication
- Familiar MySQL database environment with JDBC support (for Java-based App Engine applications) and DB-API support (for Python-based App Engine applications). It even support data import and export using
- Simple and powerful integration with Google App Engine.
- Command line tool
- SQL prompt in the Google APIs Console
The service is free for now and Google promises a 30 days notice without giving any hints on the pricing model though.
Original title and link: Google Launches Google Cloud SQL a Relational Database as a Service ( ©myNoSQL)
Most customers stated that SQL Azure delivers a reliable cloud database platform to support various small to moderately sized applications as well as other data management requirements such as backup, disaster recovery, testing, and collaboration. Unlike other DBMS vendors such as IBM, Oracle, and Sybase that offer public cloud database largely using the Amazon Elastic Compute Cloud (Amazon EC2) platform, Microsoft SQL Azure is unique because of its multitenant architecture, which allows it to offer greater economies of scale and increased ease of use. […] Application developers and database administrators seeking a cloud database will find that SQL Azure offers a reliable and cost-effective platform to build and deploy small to moderately sized applications.
There are a couple of inconsistencies in the document, but the SQL Azure case studies section is worth reading.
Back to the fun part. In the pros section:
High availability at no extra effort or cost. […] In addition, SQL Azure automatically offers built-in server and storage redundancy, a data replication solution for built-in high availability, and transparent application failover to ensure minimal disruption.
The cons section:
Zero downtime availability. Although SQL Azure supports failover architecture should a database server fail, there is some downtime, ranging from a few seconds to minutes, associated with switching the application over to another server.
Back to pros:
Scale-out capacity growth via a sharded data platform. SQL Azure offers the ability to shard data into hundreds or even thousands of logical databases, which developers can use collectively for a given application.
and in the cons:
Automatic sharding of data for extreme scalability. SQL Azure does not automatically shard data into various partitions to scale across physical servers.
Just focus only on the three case studies included in the paper (PDF).
Original title and link: Forrester report: SQL Azure Raises the Bar on Cloud Databases (NoSQL databases © myNoSQL)