3 ms·
Well if you deploy to Kubernetes it standardizes thee APIs you're using to deploy with quite a lot, then you can move around easier.
by ChatGTP 4y ago
Well if you deploy to Kubernetes it standardizes thee APIs you're using to deploy with quite a lot, then you can move around easier.
- LeBit 4y agoI've been trying very hard to sell that idea to my team. But no, they insist on using every product the different cloud providers offers. This, IMO, is a recipe to lock yourself to vendors and make maintenance and interoperability a nightmare. It feels like when devs felt they had to use all the gang of four design patterns.
- vasco 4y agoYou need to follow some engineering standard. If your engineering org is not optimising away vendor lockin, blocking someone from using tailored-feature-number-367 is unlikely to have any positive effect and you'll just make everyone move slower. If avoiding vendor lock-in is something the org cares about and is doing properly, yeah sure, enforce it, otherwise I've seen many people fighting windmills on this and bikeshedding about "not getting locked-in" when effectively many other things already lock you into that vendor.