Event Gateway vs. API Gateway

2min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

The event gateway and API gateway serve similar problems but with different approaches. The event gateway is stateful, retaining and queuing all data, allowing for data duplication, pausing, retrying, and delaying. This is beneficial for asynchronous data where specific replies are not needed. In contrast, the API gateway is synchronous and controls throughput by limiting requests per second and denying data above the limit. The event gateway model ensures data is never refused as it does not control data production.

Event-driven architecture is a software design pattern where system components communicate through events that are generated by producers, and pushed to consumers. This design is often contrasted with a request-driven architecture, where components communicate with each other by sending requests and receiving responses.

Hookdeck is an event gateway for receiving, processing, and delivering asynchronous messages. It centralizes and streamlines communication between services, like a 3rd party API such as Shopify or Stripe, and internal endpoints or other APIs.

Alex Bouchard is the Co-founder of Hookdeck. He joins the podcast to talk about event-driven architecture, building event bridges, expanding Hookdeck beyond webhooks, and much more.

Full Disclosure: This episode is sponsored by Hookdeck.

Sean’s been an academic, startup founder, and Googler. He has published works covering a wide range of topics from information visualization to quantum computing. Currently, Sean is Head of Marketing and Developer Relations at Skyflow and host of the podcast Partially Redacted, a podcast about privacy and security engineering. You can connect with Sean on Twitter @seanfalconer .