I find if there is something you cannot convince others to change with just words then you need to either make them yourself, or do a proof of concept to get bu

I find if there is something you cannot convince others to change with just words then you need to either make them yourself, or do a proof of concept to get buy in from those you are asking. Otherwise, give up and accept the way things are, or quit. I've gone the proof of concept route a lot in my career, and it's always worked and usually gives you nice organizational visibility in that you have good ideas to make things better. I also like to attach the improvements to actual numbers like "saved this much time for x devs". Maybe do new micoservices with this setup made by you, see how it goes, and then show it to them and say "look how much easier this is".