[codelust]

One example is a CMS. An article these days is a title, body and 5-10 comments, and whatever other metadata that you would want to present on a page. Don't update the corresponding NoSQL record till there are writes in the RDMBS. Serve from the NoSQL system, with at least another caching layer in front. You get the best of both worlds and just one query instead of many.

[MichaelGG]

Why not just use a materialized view inside your SQL system? No need to cache invalidation; let the system handle it for you. Same benefits, truly a single query, and only one system.

If you're going to concatenate relational data into a document, I'm not sure why a simple KV table doesn't fit the job.

[codelust]

Thanks, had to read up on what exactly is a materialized view. Not something I was familiar with.