BloorResearch.com

Transaction processing (and event processing for that matter) has always come in two flavours: simple and complex. Relational products were designed to cater for simple applications such as taking orders. If environments get too complex then the relational database schema gets too complicated to design and manage efficiently and performance degrades rapidly. However, nowadays, even simple relational applications often have performance problems as data volumes increase. So, given our industry-wide love affair with the relational database how do we get over those complexity and performance issues? The answer is that you need something that looks like a relational database, quacks like a relational database and waddles like a relational database but which isn’t, actually, a relational database.

If you have read this paper and have an opinion on it's content, please login and post a review for others to see.