eration (Citadel) and extensibility (Mixer) were all written and deployed as separate microservices. The need for these components to communicate securely and be observable, provided opportunities for Istio to eat its own dogfood (or &ldquo;drink its own champagne&rdquo;, to use a more French version of the metaphor!).</p><h2 id=the-cost-of-complexity>The cost of complexity</h2><p>Good teams look back upon their choices and, with the benefit of hindsight, revisit them. Generally, when a team adopts microser