The problem of redis isn't speed of single object storage and retrieval. We know for a fact that redis stores shit fast. And a blob of json is perfect. The pr

The problem of redis isn't speed of single object storage and retrieval. We know for a fact that redis stores shit fast. And a blob of json is perfect. The problem is multi-fold. Now you have a schema-on-read. You may spend a lot more processing time querying and accessing the data rather than getting exactly what you want from a sql query. Concurrency and locking. Constraints dbs offer. So it is important to evaluate on more than JUST read/write speed. I worked on a team that used nosql for their db needs. The performance was so terribly slow, not because of read/write speeds, but because of everything I listed above. They had to basically manually write a query optimizer vs sql. They quickly swapped to postgres and had somewhere along the lines of 10-100x performance (depending on what parts) improvements with only a week of work.