Why NoSQL is (not) Really Bad for You?

A few days ago Zeev  Rubinstein, a friend of mine, sent me cool link of Mu Dynamics Research Labs post, that described why they chose CouchDB, a leading Erlang based NoSQL product and what are their major benefits from these products:

1. Low CPU and memory utilization.
2. Map/Reduce support and usage of non normalized data model that fasten their time to market.
3. Avoiding SQL Injections. Since NoSQL systems are not widely spread, there is relatively small number of known attacks against these products. However, please notice that as NoSQL products will turn into mainstream, there will be probably new types of attacks against these products. Yet, if you are an ethical hacker, it can be a new and existing topic that maybe can turn your name to the hottest one in the industry.

Keep Performing,
Moshe Kaplan

Issuu: Erlang, Hadoop and AWS Become Mainstream

There is a buzz in the industry regarding how the Erlang, Hadoop and AWS stack enables sites scalability and how it lets them handling the demand when you hit the buzz (TechCrunch, Dig...).
An example for that is Issuu.com, a content publishing platform that is using this stack to enable millions of publications in the web and the mobiles (Android and iPhone). Tania Anderson describes this case study in a Danish article (use Google Translate for it).

In that article Issuu's CEO Michael Hansen reveal several key issues in their strategy:

1. How they managed to recruit Erlang programmers (hired talented programmers and learned them from scratch)
2. Why they favored Amazon Web Services (Microsoft Azure hardly fits the internet mainstream stacks and Google App Engine is focused on the front end while Issue needs back end processing as well), 
3. How could they avoid AWS down times (They did not. However, most of the industry was effected, so it was a non issue).

Keep Performing,
Moshe Kaplan