Why they’re still running prod on gear that’s likely thermal damaged to the point it can fail remains the obvious question.
3,613 karma · joined March 29, 2016
Why they’re still running prod on gear that’s likely thermal damaged to the point it can fail remains the obvious question.
It is kind of 'insane' but also, meh..
There's more dragons out there than we've been led to believe :}
It's a fairly concise description of the challenges ahead, and hopefully some people read it and think a bit. He didn't have to write it, I'm glad he did.
Crypto only ever allowed me to buy drugs over the internet. I'm not really buying this argument.
It will only take a few min..
I think Poland alone could defeat Russia, if it even still exists in the current form in a few years -- add the finances of France and Germany and it's even more one sided.
Postgres isn’t the answer for my workload tho we really tried, i even wrote custom sharding for our postgres and it couldn’t handle the writes the cassandra setup shrugs off, but for sure this isn’t a ‘normal’ requirement most applications have.
I’d love to use postgres, and have in various times in the past and love it (it never broke) — but one machine isn’t nearly big enough for really any of my current applications.
Mongo bit me a lot pre-wiredtiger and I refused to forgive them for years, but I'm using it again since 8.x and it's really... Boring, Scalable. There are many ways to skin a cat though, and I know not everyone has the luxury of redesigning their apps to fit the persistence layer.
What I can say though (as someone running thousands of cpus worth of cassandra at the moment); is that I deeply dislike this database. It's an operational nightmare, and I will not miss it even the slightest bit if it goes away forever.
On the other hand, I'm sure glad to see a bit of life in cassandra dev, it seems to have been dormant for a while; but would I pick it for new applications in 2026? No. I'd strongly recommend against using it unless you have the money to pay for a dedicated team to maintain it, and even then just.. No.
edit: by talk maybe i mean "speak" but I don't mean it to sound quite so harsh/jaded.. Just how most people seem to work until you know them better.
2) depends, i have a database that farks up a pretty complex distributed system when clients write from another az, latency really can be an issue for some workloads
I mean come on. The Golang team created a useful language people use for building real things — it’s easy to work with especially on large teams, and when the lack of generics turned out to be a pain point in the end (after years of production reality) they understood what the community wanted and actually… added them..
Now what, it’s not good enough?
No one forced you to use go.
No programming language is perfect. I personally find the language has served me well.
And after being so very pro generics myself, i actually find myself not even really using them that much apart from calling the slices module etc which has them under the hood anyway…
I didn’t make a profit, it’s not commercial — but apparently getting to almost break even on my energy bills is a “profit”.
Shared memory can be a problem, sure, which is why I don’t generally use that either. Erlang, of course, generally does not use shared memory outside of some cases with ETS etc which must be used carefully but i’d rather solve those problems myself.
Concurrency systems in other languages i’ve written, for example Go, there are ways to architect to avoid it also. I’d rather go slightly slower and copy be value than have to solve mutex contention and trying to make everything atomic and so on. YMMV, I don’t work in HPC just large complex busy systems.
It’s a hard/interesting problem, and harder still once you’re running across a lot of machines — but if they all get slower under the load it turns out that it’s easier to scale / work out a good balance of idle capacity to guarantee x time sla under x requests.
Fast ramp up for additional capacity is important too, but less so if you know to start the process once median execution time drops to some % of your worst target