The current database landscape can be confusing, even for experienced technology professionals. There was a time when a one-size-fits-all database system was an adequate answer to any database question, but that’s no longer true. Decisions about database systems now involve a dizzying array of application requirements, products, features, buying-criteria, and vendor claims.
This confusing environment has left application architects and strategists with a mess of confusion as they consider database technology going forward. Meanwhile, the recent explosion in database choices has fragmented the market and made it more challenging to weed through the different options. The question for many is: Is this a permanent state of affairs or a transition phase? What can we expect next, and how can application architects plan for it?