today in "things I'd never thought I'd do": arguing in favour of a NoSQL solution vs a SQL one
You must log in to comment.
in reply to @nouv's post:
for no real reason I'm inherently distrustful anytime anyone says "webscale", etc, and I associate NoSQL with that - my uninformed opinion has largely been "this seems like it's just for people who don't want to make a schema, which strikes me as failing to plan"
anyways now that i am Employed i get to deal with Technical Debt,
we have a bunch of data that is Unstructured Json Blobs and we need to be able to store 'em without worrying about creating a structure for it since that'd mean going back and destructuring/normalizing a whole bunch of historically slap-dash shit
and we only need to do a few very specific non-relational things with these blobs anyways...
so instead of spending months rebuilding everything, we could really just... store the Json blobs in some NoSQL table
long story short someone else was like "ok but why not store the json blobs in a bunch of MySQL tables" and I was like "what? huh? what?"
i definitely do not like NoSQL and i think it’s a technology invented by people who didn’t want to learn what a table is, but i did want to know if there was a valid use case and i guess there is in this case.
my workplace also has this problem but we already have the tech debt of them being stored in mysql. 