Google Megastore: Providing Scalable, HA Storage for Interactive Services(cidrdb.org)
cidrdb.org
Google Megastore: Providing Scalable, HA Storage for Interactive Services
http://www.cidrdb.org/cidr2011/Papers/CIDR11_Paper32.pdf
2 comments
The architecture of MegaStore is so complicated... There are so many roles in the system, e.g. stateless replicate server, different stateful paxos instances, stateful co-coordinator, bigtable and other auxilary roles.
I suspect some roles are added later because the original implementation does not meet their design goal, as patch to normal software product.
It is a nightmare for operation engineers of GAE.
I suspect some roles are added later because the original implementation does not meet their design goal, as patch to normal software product.
It is a nightmare for operation engineers of GAE.
There is an interesting pattern: the more scalable a data store is the larger the hassle of writing application code against it. I am lucky that MongoDB master slave has been sufficient for what I have been doing because it is almost as simple to use as a RDMS. It is clear that writing against HBase and Cassandra takes more effort and it is more difficult to be in an agile development mode.