893 karma · joined July 2, 2017
there's a bit of cyclic relationship at play here, the data changes the query plan, and the query plan affects the performance, while the performance is being optimised by the engine. if the architecture is bad then sooner or later the engine runs out of tricks and performance suffers but then nobody never is quite sure whether the current architecture's good enough.
I totally get the whole nosql that was the rage for a while... quick to prototype but I do believe once it's somewhat settled, moving the consolidated parts back to SQL is much easier to manage and optimise
To get a hint of the backdrop.. https://www.nbcnews.com/nightly-news/video/1993-rabin-and-ar...
*edit: I'd like to also comment on the crazy lighting going on.. if the photographer of this can see this comment, please take a pic of the setup..this look quite intense