Cloud Integrations, Data Architecture and MDM solutions for Enterprise Applications
summary
Examines concrete patterns: insist on save the data and return 202 before orchestration, design for 10x average load not peak, and expect auto‑scaling to take 3–5 minutes so use queues (pointed limit ~20k/sec) or Kafka/Kinesis for high throughput and replay. Recommends CDC for change capture, SNS/pub‑sub with dead‑letter and exponential backoff for retries, Saga or pull models for inventory, charge payments immediately, and enforce GDPR/PII controls plus deterministic encryption and Delta loads for recovery.
AI-written summary · about
chapters (9)
- 0:00Introduction to enterprise architecture
- 1:04Key integration challenges
- 15:49Resilient microservices patterns
- 26:04Making systems resilient
- 37:07Linking enterprise data
- 46:13Customer integration strategies
- 53:20Cloud adoption and MDM solutions
- 57:59Security and data compliance
- 1:00:07Summary and Q&A
related talks
23mDesigning Robust and Scalable Distributed Applications
29mData Mesh Streaming Patterns: A Real-time Perspective
13mLow-Maintenance Backend Architectures for Scalable Applications
30mChange Data Streaming Patterns in Distributed Systems
39mRethinking RDBMS Data Migration
42mIntegration and Conversation Patterns in SaaS Applications
01h 03mArchitectural patterns for the cloud
50mFacilitate development of complex APIs