Connectivity Patterns for Cloud Native Applications
summary
Compares four concrete connectivity patterns — APIs with API gateways and HTTP, asynchronous store‑and‑forward using brokers (AMQP/Kafka/CloudEvents) with replay, cloud services like S3 or Salesforce as middleware, and service‑network virtual routing over mutual‑TLS tunnels on Kubernetes/OpenShift (KNative examples). Shows the tooling choices and trade‑offs (security, protocol limits, enrollment, cost), demos an attempt to expose a local service through a cluster but the live demo fails to connect, and highlights when replication, durability, or automatic rerouting are appropriate.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:49From monolith to multi-cloud
- 4:39Challenges of multi-cloud connectivity
- 7:30Connectivity mesh concept
- 10:18APIs as connectivity pattern
- 12:23Event-driven with brokers
- 15:15Cloud services pattern
- 17:40Service mesh abstraction
- 22:02Demo of service network
- 25:21Trade-offs of patterns
- 26:52Tools and resources
related talks
34mDistributed applications and Kubernetes
29mCloud Native Patterns – Shifting Responsibilities
48mRethinking Connectivity
25mOperating Cloud-Native Kafka
51mExploring Stateful Microservices in the Cloud Native World
31mReverse Engineering Cloud Native: Interoperability and Community
35mComplete Idiot's Guide to Cloud Native
59mCloud patterns