The monolitic nature of embedded key-value stores based webapps makes it a poor solution for scaling horizontally. But who cares? Mind the fact, that given the

The monolitic nature of embedded key-value stores based webapps makes it a poor solution for scaling horizontally. But who cares? Mind the fact, that given the database is embedded in the webapp processus, you need some auth machinery to hit the database from the outside world anytime. Which leads to more wheel reinvention like background process scheduling like Celery. At the end of the day, embedded key-value stores are great because they require _less_ administration and have great performances but the community is fragmented and tooling is not there yet. I think embedded KV stores have still a chance in niche applications for building expert systems that require persistence but don't change a lot. For a web application which specifications (and schema) change all the time, it's a poor solution. edit: also, in the context of e.g. wiredtiger having transactions across tables like the full-text search index and plain tables is very great and save quiet a few painful experience of setting up the project.