Enabling Secure Inter-Service Communication with Tanzu Service Mesh

Enterprise software has changed significantly in the last few years. Some of you reading this may remember when most software was written as a single monolith by a small team of developers. The application had to be deployed, updated, started, stopped, and scaled as a single unit.

As software began to evolve in the early to mid-2000s, demands on software and software developers started to grow along four axes:

• Time to value: Teams were expected to deliver bug fixes, improvements, and new value-delivering features on ever-shrinking timelines.
• Elasticity: Teams needed to scale “hot” services independently and deploy individual features without having to build, test, and deploy the entire monolith all at once.
• Fault-tolerance: When an individual service failed or started to degrade, it shouldn’t affect other services, and the system should be able to work around the problematic...