4 ms·

I thought around 80% of big tech companies are still maintaining giant Java monoliths that are attached to a giant Oracle database that nobody understands. Beca

I thought around 80% of big tech companies are still maintaining giant Java monoliths that are attached to a giant Oracle database that nobody understands. Because it was all written 20 years ago, and there's no money in completely changing the architecture. I've never been able to use serverless at work. I've always wanted to, but it's too risky for most companies. In my experience, they prefer to stick to tried and tested methods that have an easily predictable budget.

KronisLV 4y ago
> I thought around 80% of big tech companies are still maintaining giant Java monoliths that are attached to a giant Oracle database that nobody understands. I may or may not know lots of people who even develop new systems that way. In part due to them not knowing better, in part due to it being an okay fit for the problem that they want to solve and in part because they haven't and won't be fired for picking what has historically been a "safe" option. More people have probably gotten burnt in the process of developing microservices and failing at it, than have been by their monoliths rotting over time and failing to scale, unless it's in an org with a strong ops culture and the support to do microservices right (with all of the tooling, like service meshes, tracing, orchestration and so on). I reckon that many out there have done nor microservices, nor serverless, nor have any interest to. They're just the silent majority: https://vadimkravcenko.com/shorts/the-silent-majority/ https://vadimkravcenko.com/shorts/the-silent-majority/