Chris Hansen

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.

A bug corrupts your critical data, how do you undo it without data loss? Your biggest customer needs to know the exact state of the system at a very specific point in time, how do you find that out? Systems using event sourcing have good answers to these questions. Event sourcing is nothing new. In fact, it's a proven pattern for building reliable systems at scale. For example, it's how most RDBMSes are implemented. Yet many developers are unfamiliar with this approach.

In this talk, we'll demonstrate how event sourcing works with examples. We'll discuss when to use event sourcing, how it relates to CQRS, and how it's a great fit for distributed systems such as microservices.

How to architect and deploy a microservice architecture on Amazon Web Services using services such as API Gateway and CloudFormation. We'll touch on a broad swath of services in the AWS suite to learn about what they do and how they fit into a microservice architecture.

First we'll look at the tools needed to build and deploy microservices on AWS with a Continuous Delivery pipeline. Then, we'll talk through some of the challenges of a distributed system and the tools that AWS provides to address them.

This talk assumes you know about microservice architecture at a high level, but assumes no prior knowledge of AWS.