It's all abt Tamil

New to this post?? Go on with  Crisps abt Scalablity Part 1  and Part 2 So are you convinced with Master Slave. Let us move on to Sharding or Shared Nothing Architecture What is it?  Before this I'll answer a different question. For Whom is it??  If the application you built can be partitioned. A scenario, You have 1 billion customers and all the customers are currently being maintained by only one data store. And they are being served from the only available data store. But the beauty of your application is there is nothing being shared between two customers. So, what is the use of it?? Just split them. Because they all are going to read data about them and they are going to write to data about them. Put up in another way, No one is going to read or write to your data except you. So, what you can do is just split your billion customers in to half a billion and make another data store to handle them. I hope now you understood what it is.  That is aw...

If you are reading this part for the first time. First go on with the previous post Crisps abt Scalability Part 1  of mine . So what are the two alien terms I mentioned earlier.  WT* is Master and Slave Architecture?? Simple as it name depicts. There ll be one master and the slaves ll listen to him. Soooorrry :P. Let me be clear. One of the implementations of master slave architecture is all writes will go only to the master and reads can be done from any of the master or slave. Ex: Redis Cache. And another way of implementation [I Hope] is master will act as a place holder of metadata about the location of data in its slaves. Ex: HBase (But this is totally different from the former, will be explained soon). What is the advantage of this???  Consistency -> [Conditions apply] How?? Simple, consider the same scenario of shopping cart. The problem was not about reading the data but writing.. right?? So, we converge all the writes to one common lo...

Hi all, It was a great day with "Cassandra - Definitive Guide". The best thing i liked abt that book is the way they explained scalability(ofcourse abt Cassandra too :P).  So,  What is scalability? It is nothing but yet another performance measure. To be clear, it is the measure on how well the application you built performs, if you add more resource to the environment it operates on. Ex. Adding more cores to processor, Increasing main memory's size, etc., Why should I care abt it? Because it is not true that if you add more resource, performance of your system(ur app) should increase. Also there is a probability that performance of your system to decrease. Can You Explain more in detail? Yes, For sure. Actually there are two ways you can scale the processing environment. Horizontally and Vertically.  Horizontally refers to adding more systems instead enhancing the existing system. Ex: Adding more web servers to serve the requests and using a load balancer ahead....

It was a boring weekend once again and I wished to author a jquery plugin for drilldown operation. Atlast I did it and commited in GIT Link to Git Repo Really awesome job by jquery team. I never felt that it is difficult to create a plugin. It was full of fun and my day passed by in a useful way :) Abt my plugin, This is a plugin which helps to implement drill down in jquery. To start working on it u need jquery latest version U need to include either jquery.drilldown.min.js/jquery.drilldown.js in your javascript src Usage: $(selector).drillDown({ animate: true; // Default 'true' *Not required container : ".divname|#spanName" //No Default values *Required listParam : "list" // Default 'list', see the demo for explanation direction : 0 // Default 0->vertical, 1->horizontal callBack : test // Default 'null', Call back function to be used on selection }); Styles: Elements inside Drill Down are li elements with c...