See MongoDB
-
This post did not contain any content.
-
This post did not contain any content.
NoSQL has always been a niche use case thing.
For some stuff, no ACID is no problem. They have their place. What I'm more suspicious of is things like Google offering distributed databases that they pretend as if they could break the CAP theorem.
-
NoSQL has always been a niche use case thing.
For some stuff, no ACID is no problem. They have their place. What I'm more suspicious of is things like Google offering distributed databases that they pretend as if they could break the CAP theorem.
wrote last edited by [email protected]And yet my Uni treats it like the biggest thing in existence. Meanwhile I've never used anything other than RDBS and Redis (only for cache), neither in private nor at work.
-
And yet my Uni treats it like the biggest thing in existence. Meanwhile I've never used anything other than RDBS and Redis (only for cache), neither in private nor at work.
MongoDB is huge though for all the wrong reasons, businesses think that just because it's JS, they can just have frontend devs - sorry, they are "fullstack" now - doing DBA work.
I worked as one of two NoSQL DBAs for a Fortune 50 finance company, and there is a ton of CV-driven development going on giving NoSQL a bad name. Most use cases don't need NoSQL. And for those which do, NoSQL is almost always harder to implement than simple SQL based RDBMSs.
-
This post did not contain any content.
Or does writes to S3 via LSM
-
And yet my Uni treats it like the biggest thing in existence. Meanwhile I've never used anything other than RDBS and Redis (only for cache), neither in private nor at work.
Sharded RDBS gets you very very far from my experience at least.
-
This post did not contain any content.
If that is what it takes to get these kick-ass benchmarks.
-
If that is what it takes to get these kick-ass benchmarks.
Amazing video
-
And yet my Uni treats it like the biggest thing in existence. Meanwhile I've never used anything other than RDBS and Redis (only for cache), neither in private nor at work.
wrote last edited by [email protected]If you need to run queries that aggregate big amounts of data in a reasonable time and cost, you'll need something built for it. For example, with a column oriented file format instead of the row oriented file format found in traditional relational databases
-
MongoDB is huge though for all the wrong reasons, businesses think that just because it's JS, they can just have frontend devs - sorry, they are "fullstack" now - doing DBA work.
I worked as one of two NoSQL DBAs for a Fortune 50 finance company, and there is a ton of CV-driven development going on giving NoSQL a bad name. Most use cases don't need NoSQL. And for those which do, NoSQL is almost always harder to implement than simple SQL based RDBMSs.
Jumping in this, bingo. JavaScript only shops scare the fuck out of me.
-
If you need to run queries that aggregate big amounts of data in a reasonable time and cost, you'll need something built for it. For example, with a column oriented file format instead of the row oriented file format found in traditional relational databases
My point is more that 90% of use cases don't need that, and for those that do, you can't just slap eg. Cassandra at it and pretend it's a relational database.
-
Sharded RDBS gets you very very far from my experience at least.
Definitely, and I'm saying that while my jobs were mostly on NoSQL and I love doing it.
-
This post did not contain any content.
But it's webscale
-
If you need to run queries that aggregate big amounts of data in a reasonable time and cost, you'll need something built for it. For example, with a column oriented file format instead of the row oriented file format found in traditional relational databases
And the key word โbigโ here is far bigger than most engineers need to deal with. Hell, most supposed โbig dataโ problems Iโve seen people try to tackle are small enough to fit the whole database into memory.
-
Jumping in this, bingo. JavaScript only shops scare the fuck out of me.
Just wail til they become AI-generated-JavaScript-only shops. They're gonna be vibing like the Tacoma Narrows Bridge.
-
This post did not contain any content.wrote last edited by [email protected]
Every time I'm assigned to a project that uses a document database
"So how are you guys handling all your related data?"
Finds collection of massive JSON documents containing all the related data
"Oh boy."
-
NoSQL has always been a niche use case thing.
For some stuff, no ACID is no problem. They have their place. What I'm more suspicious of is things like Google offering distributed databases that they pretend as if they could break the CAP theorem.
What's ACID?
-
This post did not contain any content.
This is kinda absolute BS at this point, though.
Mongo has acid transactions, and has for years now. Although this is only within the same database, there are plenty of dbms (including rdbms) that don't support cross-database transactions.
Mongo also, since time immemorial, has had "write concern" to ensure that it's written to disk (to the journal) before the transaction is completed.
-
What's ACID?
https://en.m.wikipedia.org/wiki/ACID
Atomicity (something happens in its entirety or not at all), consistency (database is always in a valid state --- if the database has constraints, they will always be honored), isolation (transactions don't step on each other), durability (complete transaction is complete even if there's a power failure).
Not a database expert, my parenthetical explanations may need work.
-
But it's webscale
wrote last edited by [email protected]Wow, that video is 15 years old!
