Technology blogs for Developers by Developer.

We increasingly live in a world where data doesn’t fit nicely into the tidy rows and columns of an RDBMS. Mobile, social, and cloud computing have spawned a massive flood of data. 80 percent of all enterprise data as unstructured. What's more, unstructured data is growing at twice the rate of structured data. As the world changes, data management requirements go beyond the effective scope of traditional relational databases. The first organizations to observe the need for alternative solutions were Web pioneers, government agencies, and companies that specialize in information services. Increasingly now, companies of all stripes are looking to capitalize on the advantage of alternatives like NoSQL and Hadoop: NoSQL to build operational applications that drive their business through systems of engagement, and Hadoop to build applications that analyze their data retrospectively and help deliver powerful insights. Enjoy !!!!!!

How To Choose A NoSQL Database? NoSQL databases are now part of web-scale architecture. The question is when to use what? Below, I try to compare the NoSQL data stores that I have worked with. Hopefully, it would be useful for programmers exploring and deciding the technology for their web-scale application. When to use NoSQL Before deciding on to use NoSQL instead of a SQL technology, you should ask yourself following questions about your use case (includes  ACID  test of your application) : Transactions vs No transactions (Do you need atomicity?) [Most NoSQL databases don’t support transactions] Consistent or eventual consistent (Are you okay with eventual consistency?) [Most support configurable consistency mode. You should test your scale with the consistency mode your application requires. For example, your performance test holds no good when done on “eventual consistency” mode and you decide to use hard consistency for your application.] Vertical vs horizontal