Michael MacTaggert is a software developer looking for work, host of a law review podcast called Amicus Lectio, and a moderator of Programming Discussions (invite.progdisc.club). Follow me on Twitter!
A company I used to work for started using QlikView for all their data dashboarding and actively resisted pleas from my manager to even investigate different stacks. Cut to several years later, they have me writing a "big data" application in QlikView, which is a tool that holds all of its data in RAM and forces all active dashboards to share that RAM, and it Did Not Work.
Michael MacTaggert is a software developer looking for work, host of a law review podcast called Amicus Lectio, and a moderator of Programming Discussions (invite.progdisc.club). Follow me on Twitter!
A company I used to work for started using QlikView for all their data dashboarding and actively resisted pleas from my manager to even investigate different stacks. Cut to several years later, they have me writing a "big data" application in QlikView, which is a tool that holds all of its data in RAM and forces all active dashboards to share that RAM, and it Did Not Work.
So... Aside from the sharing issue, if the power goes out, data goes bye bye, right?
The data was usually pulled from somewhere else, and you couldn't add data on the fly, so that wasn't a problem so much.
But if one app went down, it took all the rest on that machine down with it.
...There was (pretty much) one machine.