[nerdponx]

This sounds pretty typical for "analytics" workloads, which relational databases handle just fine. Maybe by "noSQL" they just meant something with column-oriented storage? But even that seems like it might be overkill, compared to setting up a couple of denormalized "analytics tables" to avoid the cost of complicated joins.

[yrgulation]

Yeah with all due respect but hacks like these are a bit amateurish. I heard of a dude i think at intuit building their queues in a relational db because they work “just fine”. Prompted a giggle or two. Use the right tool for the task at hand, dont do clever hacks as they bite back later on.

[jvolkman]

"works just fine" might be a perfectly reasonable tradeoff if it avoids adding additional architectural complexity.

[yrgulation]

Depends what you define as complexity. What i described is trivial. Unless the userbase and or data are small.