We deploy to production over 100 times a day

I really wonder how an HTTP application doesn't suffer from performance hits when it's based on 2000 micro services. Lets say even just 30 of those get used by a call to monzo.com. How does this not cause at least let's say ~300ms delay? I guess all the calls actually come from a local memory cache and there is almost never a real http call made to these microservices. Otherwise I have no idea how microservices are ever viable.

Where I&#x27;ve worked, we would use Jenkins for &quot;Continuous Delivery&quot; but then require upper management signoff for every single damn change.<p>&quot;We don&#x27;t have time to test&quot; -&gt; Production poopfires -&gt; &quot;We need an out of band code review process&quot;<p>The faces on these people when one proposes deployment in terms of basic git triggers on protected branches.

This is comical. Your company needs 3,000 deploys a month? You deliver 3,000 features a month? Your BAs&#x2F;PMs identify 3,000 <i>useful</i> features a month? This isn&#x27;t trolling - this is a call out of the absurdity you are presenting as a positive.