Embracing async
Synchronous API calls are inherently more resource-intensive than queuing up an async message, and the failure scenarios can be complex. Yet, most developers use synchronous REST or RPC for inter-app communication without questioning it. What would our applications look like if we used asynchronous messages, or events, to send messages from one app to another by default?
In this talk, we'll explore some common use cases to see whether synchronous or async would be a better fit and what the tradeoffs are. Finally, we'll take a high-level look at how companies are embracing async using event stream processing and workflows.
About Chris Hansen
Chris Hansen is a technology leader and software architect with experience working on web applications of all shapes and sizes, from static sites in the 90s to a billion-dollar e-commerce platform and covering a lot of ground in-between. Chris started his career at Overstock.com, where he helped them break up their monolithic web app into services at scale. Since then, he has been working on microservice architectures at some tech startups in the Salt Lake City area, aka Silicon Slopes. As CTO of PeopleKeep, Chris built the product team that created the PeopleKeep platform from scratch and helped it grow to millions in revenue.
More About Chris »