Arbitraging Capacity for Spiky Traffic

1min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

Utilizing a deck for arbitraging the capacity to manage spiky traffic efficiently by scaling up resources to handle spikes in customer volume over short time spans. This engineering work and capability are crucial to deal with aggressively spiky traffic, ensuring the ability to process such spikes and implement best practices around security and processing, especially regarding the verification of webhooks sent out. The responsibility extends beyond scale to include best practices and security, recognizing that API consumers may lack the engineering resources to address these issues.

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 .