3 ms·
I often make a similiar joke when I am struggling with microservices related bugs or architectural designs. 1: Just use apache + php 2: Use microservices, ser
by BozeWolf 3y ago
I often make a similiar joke when I am struggling with microservices related bugs or architectural designs.
1: Just use apache + php
2: Use microservices, service meshes, k8s etc.
3: Just use apache + php
Cheap joke though, although it was fun, applications and demands have changed. Especially in the environments I work in today. Although I often, as an excersize, question myself why stuff got so complicated and if this really is the way it should work. And tbh, sometimes the answer, in my opinion, is no.
- ghusto 3y agoRight? I had a lot of fun learning K8s for a client. Every new thing I learnt made me think it was even cooler. Then the first maintenance came. _"Not worth it"_ doesn't even begin to cover it. If you have both: a) Well designed microservices that follow the 12 Factor App principals _fully_ b) A team of (minimum) five to dedicate solely to K8s maintenance Sure, go for it. How many people using K8s can tick both of those though? If you want something reliable, easy, and (almost) maintenance free; Just use AWS Lambda + API Gateway (or whatever Google and Microsoft equivalents you have).
- slowmovintarget 3y agoOr AWS ECS instead of Kubernetes.