2 ms·
The problem here is K8s, to be honest. Microservices as an architecture has become synonymous with K8s deployment. K8s is overkill for anything that is smaller
by marcus_holmes 6y ago
The problem here is K8s, to be honest. Microservices as an architecture has become synonymous with K8s deployment. K8s is overkill for anything that is smaller than, say, Twitter.
But it's cool, so everyone wants to use it, so suddenly we get bullshit like TFA.
It's like Agile. Agile has some great ideas. But now when people say "agile" they mean Scrum. And Scrum is so badly implemented in most places, used as an excuse to do all the things that the Agile Manifesto tried to warn us about in the first place. We end up at shittily-organised micro-waterfalls and everything is crap, but somehow that's "Agile".
Same for microservices. There's some good ideas there, but most of the time it's implemented so badly, increasing complexity and reducing managability. We end up with thousands of lines of spaghetti YAML organising god-knows-how-many of instances of god-knows-what when all we needed was a simple webserver, file store and database. And somehow that's "better".