The choice of database for production level projects is a critical decision that we need to make at the initial stages of the project. Most of us do the mistake of choosing databases by simply going through the features list,popularity,official docs and couple of benchmarking results on random sites without giving much thought to choosing database based on the problem we are actually trying to solve or the type of projects we are undertaking in future. Matter of fact is one needs to do proper benchmarking and load/stress testing before picking up dbs, go through docn and understand whether available schema design and queries are suitable for one's project. We too made the mistake of choosing couchbase in production once eventually realizing that it was not suitable for our requirements and switched to redis eventually at the time when our applications were in production. This kind of migrations do take a lot of time and efforts but sometimes are inevitable to tackle performance issues. I completely agree that sometimes sql databases are just good enough and provide proper structure to database schema design and might be suitable rather than trying to bother about faster read times :D