Go event-driven with AWS Lambda & Event Mesh
summary
Claim: an event mesh built with Solace event mesh routes protocol‑translated events between brokers in three AWS regions (Singapore, Ohio, Ireland) and integrates with AWS via a CloudFormation deployment that provisions a broker, API Gateway and connects to Lambda, Kinesis, SQS/SNS. Demo shows MQTT bus telemetry (bus 1024 and 1025) streamed into Ohio after subscribing, CloudFormation finishes in ~10 minutes, Lambda enriches events and writes to Elasticsearch/Kibana, and the dynamic subscription routing works as shown.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:33What are events
- 2:10What are tap events
- 3:00Why organizations are becoming eventdriven
- 3:30What is an event
- 3:42Challenges
- 4:05Technologies
- 4:26Realtime event distribution
- 5:00Event Mesh
- 6:39Service Mesh
- 7:13Use Cases
- 9:29Demo Application
- 10:46AWS Services
- 11:44How it works
- 12:30Demo
- 12:55API Gateway
- 13:15Lambda Function
- 14:22Lambda Subscriptions
- 15:00Lambda Events
- 15:24EventDriven Architecture
- 16:12Outro
related talks
43mUse Solace & AWS to Create a Global EDA Backbone
26mService Mesh, Serverless and Event Drive
47mEvent-driven Serverless Architecture with DynamoDB
27mGoverning the Cloud Native Event Bus: Applying ServiceMesh to Knative Eventing Workshop (Part 2)
48mYou need Event Mesh, not Service Mesh
38mEvent-driven Architecture
45mBuilding Event-driven Serverless Applications
43mRealtime Serverless Communication with