this post was submitted on 14 Feb 2026
349 points (98.1% liked)
Programmer Humor
29749 readers
232 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The worst DB in existence, not to defend Oracle, is blockchain.
y'all wrong, the worst database in existence is wherever I keep my notes. because every time I write notes I forget where the fuck I wrote them.
Isn't it how all the databases work? Or maybe you should just enable cache for yours.
can't cache my notes because I forgot where I put my notebook
Based on what? It’s top notch for immutability, zero trust, proof of existence, accountability, transparency, uptime, decentralization, network resilience…
What about throughput, latency, schema modeling, query load balancing/routing, confidentiality, regulatory compliance, operational tooling? How easily can I write a CRUD or line of business service using it?
Confidentiality, regulatory compliance, schema modeling (IDLs?), query load balancing (rpc infra) and operational tooling pretty good in my world now (Solana). Throughout and latency decent now (400ms conf, couple second finality, 4k tps) but obviously the type of system that needs a trustless immutable database has tradeoffs.
How easily can you write a crud system? No clue that’s on you. A line of business service? Why the hell would that need a trustless immutable ledger. You’re barking up the wrong tree. Low level financial systems are pretty much the only thing that benefits. Small niche for proof of existence perhaps. And maybe other immutable use case things.
Blockchain isn't a Database, and the worst one is AS400.
A400 is at least relational.
MongoDB on the other hand...
I am a big SQL fan but not all data has to be relational.
Let’s say I want the GPS coordinates of ten million vehicles every 5 seconds. I have a vehicle id, a timestamp, and coordinates. I do not care if a few writes get lost. Why does this have to be relational?
And perhaps I also record other info that may change from vehicle to vehicle. Perhaps just values that are true if present. DoorOpen, BrakeApplied, LightsOn, LightBarOn, EngineOn, etc. I may only be displaying this data in a UI. I may get different values from every vehicle or even every write. There is no “schema”. I mean, I can have a JSON field or something in my relational table? But this is not exactly relational anymore.
Correct not all data has to be relational but it will always eventually become relational. You will at one point want to pair that vehicle id to a vehicle and then again to something else.