In my experience, one of the major bottlenecks in building an Application lies in the database. This crucial piece of your app is also the most difficult to alter. If you have high availability software, how do you improve from spaghetti code without being able to do major changes to its database? You may refactor your spaghetti into beautiful, hexagonally layered lasagne, but if your database sucks, your data sucks.
In this talk you will learn how to improve your legacy application by discovering the benefits of NoSQL to consolidate your data, and how MapReduce can increase your project performance.
----- talk info -----
Many people talk about refactoring code, and we ask someone about the database they say: "If you abstracted your models well, you don't need to worry about it", but in many cases, this is not reflect the real world.
This is why I want to talk about it. To show what can you do to make your DB more suitable for your application.