RDBMS isn’t going anywhere soon.
Greg Young wrote an opinion piece that partially blames incorrect or failing systems on development teams that don’t spent enough effort thinking how they will persist data. Your not carefully deliberating whether or not to throw out all your rdbms database tooling, training, and experience? Shame on you says Greg.
Why are you not just using an Object Database or a Document Database?
Every choice outside of traditional RDMS databases completely lack:
- Huge vertical of management studio like tooling available for things like MySql or Sql Server
- Scores of developer experience and talent.
- Proven data safety and backup techniques.
- Proven scalability and optimization techniques.
- Functional ORM libraries for data access and retrieval for almost any language or rdbms combo.
It pains me to no end that developers more often than not make the single largest architectural choice on their system without applying any rigor to the decision
While reading his opinion piece I get images of NASA contemplating sending the next space shuttle up in a slingshot or trebuechet. Of course I don’t site down and have a chat with myself or the team I’m working with about whether a key/value store is worth it. There would have to be a killer reason or feature to use a storage system outside of a RDBMS or some type of insurmountable scaling need that only a key/value store could solve.
The reason developers don’t discuss these things is because its not even a discussion worth having.
I spent my weekends throwing away my RDMBS snuggle blanky comfort zone to check out things like CouchDb and other key/value stores. But when I have client data that can’t be lost or productivity goals that need to be met I can’t even consider using a barely proven technology.

