So, who would take responsibility for a service mesh in a typical IT organization? The answer varies. In the legacy world, service mesh models used to belong to developers during the times of monolithic applications and SOA/ESB applications. In a cloud-native environment, the service mesh has moved from Dev to Ops, and this is a significant shift because it lets the developers focus on their specialty, developing applications, and provides important services to them without them having to think or understand how they operate.

Google started a new practice known as Site Reliability Engineering (SRE), which the service mesh may fall under.

Now, let's discuss basic and advanced service mesh capabilities.