Role of App Integration in Cloud Native & Microservices Landscape
summary
Integration remains central to cloud native systems, not optional, because 80% of services call other services so composition and messaging logic moves into each service. Service mesh (sidecars + control plane) offloads circuit breaking, auth, observability but does not replace business composition or saga-style compensations for distributed transactions. Expect to use Docker/Kubernetes, Prometheus, Kafka/AMQP, gRPC/HTTP, and frameworks like Apache Camel K, Spring Boot, WSO2 Micro Integrator and Ballerina; these cloud‑native tools aim to work in practice for the patterns described.
AI-written summary · about
chapters (19)
- 0:00Start
- 3:36Integrating Cloud native apps?
- 4:31From ESB to 'Smart-endpoints and Dumb Pipes'
- 8:59Building Smart-endpoints
- 13:16Service Mesh vs ESB?
- 14:39Requires a cloud native runtime
- 15:11Service Orchestrations (Active compositions)
- 16:36Service Choreography (Reactive compositions)
- 16:52Service Choreography/Reactive compositions
- 19:26Protocols abstractions
- 20:54Integration Patterns
- 21:41Resiliency
- 22:43Message Delivery Semantics
- 24:02Type Conversions
- 26:01APIs, Events and Streams
- 27:21Integrating with SaaS and legacy on-prem
- 27:50Workflows and SAGAS
- 29:30Integration Frameworks
- 33:06Summary
related talks
08mThe Evolution of Microservices Architecture in Cloud-Native
37mDistributed applications and Kubernetes: Frameworks or service meshes or both
31mSharing is caring: Building a modern microservice architecture helps everyone get ahead
30mApplication integration patterns for microservices
50mFacilitate development of complex APIs
27mCloud Native: why, oh why?
35mAdvanced Microservices Architectures
46mWhat Next After Microservices?