A Look Back at Enterprise Integration Patterns
summary
Argues Enterprise Integration Patterns remain useful for serverless, demonstrates wiring Apache Camel routes into Azure Functions and running Camel itself as a function, shows a live Camel Twitter pipeline that splits tweet JSON, throttles, deduplicates, sends images over WebSocket and writes messages to Kafka, and confirms end-to-end flow works locally and deployed to Azure. Notes Camel has 50+ components and cloud functions often give ~1M free requests/month so cost scales by executions.
AI-written summary · about
chapters (6)
- 0:00Start
- 21:24Monoliths to Microservices to Functions
- 22:11Integration Problems
- 24:59Another example. Guess the pattern name!
- 35:15Solutions for Application Integrations • Integration Frameworks
- 35:41Camel and Serverless Functions
related talks
43mCloud Native My Camel: from Low Code to Pro Code, inject Serverless & Cloud Native Goodness...
30mApplication integration patterns for microservices
53mPatterns and practices for developing enterprise-scale applications with serverless
01h 01mEvent driven applications in Azure
39mIntroducing Azure Functions for serverless .NET
37mBuilding Cloud Integration Applications Through Knative and Apache...
54mDeveloper Fundamentals of Serverless NET Development with Azure Durable Functions
42mBuild a Real-Time Event-Driven Java Solution in Azure