Top 5 Challenges in Service Mesh Adoption at Enterprise
summary
Sberbank adopts Istio on OpenShift to move a legacy bank platform to a service mesh, proving a pilot becomes production in about six months with a real workload of 5000 transactions per second. Main obstacles are strict security zones and identity systems, latency and scalability tuning that lead to an Istio + OpenShift 4.3 configuration, and many integration patterns from “no change” adapters to replatforming. Adoption needs sustained knowledge transfer with IBM and operational playbooks; next step is a multi-cluster control plane for single discovery and management.
AI-written summary · about
chapters (6)
- 0:00Intro
- 1:20Mapping security requirements
- 2:52Performance and availability
- 4:55Integration with other systems
- 6:35Internal client resistance
- 7:23Skills and expertise
related talks
59mDivide and Conquer: Tackling Microservice Challenges with Istio Service Mesh
41mService Mesh beyond single clusters
47mDeploying Service Mesh in Production
55mEmpower Your Microservices with Istio Service Mesh
40mReimagining Application Networking and Security
35mAdvanced Microservices Architectures
45mIstio Service Mesh Simplified Beyond a Single Cluster
34mIstio Performance and Best Practices in Large Scale...