GOTO EDA Day 2024 - Warsaw
User interfaces by their nature are event driven - interactions trigger events that drive the application. But integrations between frontend and backend are often built synchronously using a request/response pattern. This session explores patterns to enable asynchronous, event-driven integrations with the frontend. It's designed for architects, frontend, backend, and full-stack engineers. You will leave with real-world patterns that bring the agility and responsiveness of EDA across client-server interactions.
GOTO EDA Day 2024 - London
User interfaces by their nature are event driven - interactions trigger events that drive the application. But integrations between frontend and backend are often built synchronously using a request/response pattern. This session explores patterns to enable asynchronous, event-driven integrations with the frontend. It's designed for architects, frontend, backend, and full-stack engineers. You will leave with real-world patterns that bring the agility and responsiveness of EDA across client-server interactions.
AWS re:Invent 2023
Developers are building large-scale distributed applications that communicate between each other and clients via REST, GraphQL, WebSockets, and other means. Building effective APIs includes both a strategy and a means to communicate developer-level API details. In this session, learn about access patterns and how to evaluate the best API technology for your applications. The session considers the features and benefits of Amazon API Gateway, AWS AppSync, Amazon VPC Lattice, and other options.
AWS re:Invent 2022
This session explores how to think about security from the front to the back of a typical serverless application. How do you configure AWS serverless services to provide least-privileged access while helping to ensure functionality? How should you think about managing IAM policies for your AWS Lambda functions? This session covers all of this and more, leaving you with concrete examples applicable to almost any workload.
AWS re:Invent 2020 (virtual)
Serverless technologies introduced new ways to build highly scalable, resilient applications without managing infrastructure. When building serverless applications by using several managed services, how should you handle errors? Should you include a try/catch block in your code or let the service deal with errors? What if the function is invoked as a task in an AWS Step Functions state machine? Can AWS Lambda Destinations help? In this session, explore error handling across Lambda invocation models and discuss patterns for proper visibility and retry behavior. Leave this session with a better understanding of how to code and/or configure services to better deal with errors across different use cases.
