Apidays Virtual Helsinki - Przemek Kulik, SoftwareAG
summary
Service mesh is useful but stops at the network/L4 layer; this solution adds application/API context on top of Istio by wiring an API gateway into the control plane and injecting a micro gateway sidecar at runtime. It enforces JWT-based security, content-based routing, payload transformations and data masking without changing service code, provides visibility and a central governance plane across multiple meshes, and the e‑commerce demo for personalization and adding a new brand microservice works as described.
AI-written summary · about
chapters (6)
- 0:00Start
- 5:18MICROSERVICES ARE REPLACING THE MONOLITH
- 10:02SERVICE MESH IS BECOMING MORE PREVALENT
- 14:48TAKEAWAYS WHAT PROBLEMS DOES THE APPMESH SOLVE?
- 17:16BRAND FACTORY A CASE STUDY
- 19:00APPMESH DEMO SCENARIOS
related talks
53mDo you need a Service Mesh?
40mReimagining Application Networking and Security
24mTransform Your Network: Master API Control & Security
45mService Mesh Security: Shifting Focus to the Application Layer
17mDesigning a Service Mesh for Global Scale At SAP
32mIstio: Weaving the Service Mesh [I]
42mAmbient Mesh: new sidecar less & faster Istio for zero trust
29mZero Trust for APIs: From Edge to Mesh with Istio