14. ● “Realtime data-flow engine” (L7 Proxy)
● Events (data) → Functions (serverless compute)
● API Gateway & Pub/Sub
● Run FaaS on any provider → Cross-cloud applications
● Extensible through middlewares and plugins
● Hosted version / On-Prem
What is the Event Gateway?
16. Goals
● Express all data as events
● React to any event, with any FaaS, in any location
● Be flexible, develop fast
● Accommodate many use-cases
● Decouple logic
● Decouple teams
17. Express all data as events
● Receives data via HTTP and
interprets it as an event
● Ingests custom event schemas
● Ingests HTTP requests as events
● Emits logs, metrics & errors as events
Data
18. ● Any event
● Supports major FaaS providers
● Discovery
● Composition
● Communication
React to any event, with any FaaS, in any location
AWS
Lambda
Azure
Functions
Google Cloud
Functions
20. Be flexible, accommodate many use-cases
Pub/Sub
HTTP
request with
special
headers
Request body
is converted to
an event
21. Be flexible, accommodate many use-cases
Pub/Sub
HTTP
request with
special
headers
Request body
is converted to
an event
API
Gateway
HTTP
request
Request is
converted to
an HTTP event
22. Be flexible, accommodate many use-cases
Pub/Sub
HTTP
request with
special
headers
Request body
is converted to
an event
API
Gateway
HTTP
request
Request is
converted to
an HTTP event
Webhooks
HTTP
request from
a supported
integration
Event
Gateway
knows what to
do