Microservices architectures have been increasingly celebrated as a way for enterprises to become more agile, and deliver applications that keep pace with changing customer needs. However, with adoption comes the complexity of managing a large number of microservices, and doing so demands empowering developers to focus on what microservices do rather than how they are doing it. The complexity gets compounded further when enterprises want to increase microservices consumption throughout the organization or with external developers and partners.
For an enterprise to maximize its microservices strategy, it needs both a service mesh to help simplify the complexity of a growing network of microservices, and API management to increase consumption and extend the value of microservices to new collaborators.
When you tune in, we will show you how:
Istio, an open source independent service mesh, provides the fundamentals you need to successfully manage service interactions across container and VM based workloads
Istio users can expose one or more services as APIs by adding API management capabilities via Istio’s native configuration mechanism
Apigee users can add Istio to their existing Apigee installation, and then move microservices into the service mesh, and
Istio’s Mixer plugin model enables new rules and policies to be added to groups of services in the mesh without touching the individual services or the nodes where they run.