OR, i can open a file stream, serialize my data to JSON, entity by entity, and dump all to a file.
The good old file.
Your position can be applied to all databases. Why not abandon them all and just use CSV ?
Personally, I never got into the hype with the NoSQL and for me the only use is as a convenient API for storing JSON files during prototyping so that I can later decide how my data should be structured.
Definitely tech debt for the future but fast iterated design that needs the database stuff fixed has more chance for success than the rigid design with the perfect data architecture.
NoSQL or classic RDBMS, these tools give you ways to manage your data on the filesystem(or in the memory?). You can spend time to write a code that processes files in a folder or you can use the software that does it for you. You can write a code that relates two files in a folder or you can use a software that already can do it and you can just ask that software for the outcome.
When it comes to "read" the data, you read it only from processed database that can be anything.
Since you can do your processing completely independently of your web server, your are not necessarily pushing your computational load from the DB to the web server.