Posted in March 5, 2010 ¬ 7:44 amh.Royans
Unless you are running a fly by night shop, DR (Disaster recovery) should be one of the top issues for your operations team. In a “Scalable architecture” world, the complexity of DR can become a disaster in itself.
Yesterday Google Announced that it now finally has DR plan for Google Apps. While this is nice, [...]
Read the rest of this entry »
Posted in March 1, 2010 ¬ 9:30 pmh.Royans
Reddit has a very interesting post about what not to do when trying to build a scalable system. While the error is tragic, I think its an excellent design mistakes to learn from.
Though the post lacked detailed technical report, we might be able to recreate what happened. They mentioned they are using MemcacheDB datastore, with [...]
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 3, 2010 ¬ 1:27 amh.Royans
Networking devices on the edges have become smarter over time. So have the firewalls and switches used internally within the networks. Whether we like it or not, web applications over time have grown to depend on them.
Its impossible to build a flawless product because of which its standard practice to disable all unused services on [...]
Read the rest of this entry »
Posted in January 31, 2010 ¬ 5:29 pmh.Royans
While “private clouds may not be the future” they are definitely needed today. Here are some of the top issues bothering some organizations which have been thinking about going into the cloud. Some of issues were based on Craig Bolding’s talk on “Guide to cloud security”.
Unlike your own data center, you will never know [...]
Read the rest of this entry »
Posted in January 25, 2010 ¬ 12:23 amh.Royans
James Hamilton is one of the leaders in this industry and has written a very thought provoking post about private clouds not being the future. This is what he said about private clouds when compared to existing not-cloud solutions.
A fix, Not the future (reference to an InformationWeek post)
Runs at lower utilization levels
Consumes more [...]
Read the rest of this entry »
Posted in January 23, 2010 ¬ 11:13 pmh.Royans
Designing any scalable web architecture would be incomplete without investigating “load balancers”. There used to be a time when selecting and installing load balancers was an art by itself. Not anymore.
A lot of organizations today, use Apache web servers as a proxy server (and also as a load balancer) for the backend application clusters. Though [...]
Read the rest of this entry »
architecture, haproxy, highavailability, loadbalancer, perlbal, scalability, varnisharchitecture, haproxy, highavailability, loadbalancer, perlbal, scalability, varnish
Posted in January 18, 2010 ¬ 9:13 pmh.Royans
I’m so locked up in my own java world that I didn’t realize something as cool as this existed in the ruby world.
Heroku is the instant ruby platform. Deploy any ruby app instantly with a simple and familiar git push. Take advantage of advanced features like HTTP caching, memcached, rack middleware, and instant scaling [...]
Read the rest of this entry »
Posted in July 17, 2009 ¬ 11:18 pmh.Royans
Products/Ideas
redis – http://code.google.com/p/redis/ : Redis is a key-value database. It is similar to memcached but the dataset is not volatile, and values can be strings, exactly like in memcached, but also lists and sets with atomic operations to push/pop elements.
HBase – http://hadoop.apache.org/hbase/ : HBase is the Hadoop database. Its an open-source, distributed, column-oriented store modeled [...]
Read the rest of this entry »