Posted in February 27, 2010 ¬ 12:51 amh.Royans
Few weeks ago while I was mulling over what kind of service registry/discovery system to use for a scalable application deployment platform, I realized that for mid-size organizations with complex set of services, building one from scratch may be the only option.
I also found out that many AWS/EC2 customers have already been using S3 and [...]
Read the rest of this entry »
Posted in February 26, 2010 ¬ 8:12 amh.Royans
This is a very interesting talk by Jonathan Ellis on database scalability. He designed and implemented multi-petabyte storage for Mozy and is currently the project chair for Apache Cassandra.
What every developer should know about database scalability, PyCon 2010
View more presentations from jbellis.
Scalability is not improving latency, but increasing throughput
But overall performance shouldn’t degrade
Throw [...]
Read the rest of this entry »
Posted in February 14, 2010 ¬ 3:33 pmh.Royans
Large distributed systems run into a problem which smaller systems don’t usually have to worry about. “Brewers CAP Theorem” [ Ref 1] [ Ref 2] [ Ref 3] defines this problem in a very simple way.
It states, that though its desirable to have Consistency, High-Availability and Partition-tolerance in every system, unfortunately no system can [...]
Read the rest of this entry »
Posted in February 6, 2010 ¬ 3:14 pmh.Royans
Cassandra is the only NOSQL datastore I’m aware of, which is scalable, distributed, self replicating, eventually consistent, schema-less key-value store running on java which doesn’t have a single point of failure. HBase could also match most of these requirements, but Cassandra is easier to manage due to its tiny footprint.
The one thing Cassandra doesn’t do [...]
Read the rest of this entry »
CAP, NOSQL, cassandra, database, eventually consistent, scalableCAP, cassandra, database, eventually consistent, NOSQL, product, scalable