From Monoliths to Modern Integration Platforms
summary
Argues that modern integration platforms must balance developer autonomy with security by design and provide versatile tools like Kafka and Camel-style EIP modules. Shares concrete lessons from a GCP rollout: multi-logical environments feature is unused, an encrypted-secrets-in-git pipeline corrupted entries and was abandoned, running FTP brokers on Kubernetes worked but felt wrong, and Terraform plan/apply service-account permissions become a complex attack surface. Warns about practical pitfalls: retries causing duplicate writes, DLQ reordering, and timeout cascades.
AI-written summary · about
chapters (8)
- 0:00Integration platforms
- 3:48Monoliths to modern needs
- 7:23Autonomy agility and security
- 13:43Lessons from building platforms
- 18:28Security principles
- 25:58Pipeline security challenges
- 30:13Versatility with tools
- 42:45Conclusion and future
related talks
33mFireside chat - Monoliths, Microservices & Modernization – Practical Strategies
29mSecuring the platform: Hard-won lessons from the teams who've been breached, scaled, and survived
50mMajestic Modular Monoliths
46mLove Your Monolith
01mSecuring and connecting both traditional and modern applications
14mArchitecting Secure and Scalable Integration Platforms for FinTech
21mIncorporating Security into Platform Engineering: The Dos and Dont’s
01h 01mCloud Integrations, Data Architecture and MDM solutions for Enterprise Applications