Presentation: Designing Events-First Microservices
This presentation is now available to view on InfoQ.com
Watch videoWhat You’ll Learn
- Understand the goals and needs of an events-first architecture.
- Hear how event-driven system increase certainly, resilience, scalability, traceability, and loose coupling.
- Gain a better understanding of the tools and techniques of event-driven microservice architectures.
Abstract
- increase certainty
- increase resilience
- increase scalability
- increase traceability
- increase loose coupling
- reduce risk
Skeptics should definitely attend.
How would you describe the persona and level of the target audience?
My talk is for programmers and architects (from beginners to experienced) that are interested in and intrigued by event-driven systems and event-driven architecture.
What do you want “that” persona to walk away from your talk knowing that they might not have known 50 minutes before?
I will try to give them a theoretical understanding what being event-driven is all about, with enough practical tips to get started applying it to their use-cases, design process, and system architecture.
What trend in the next 12 months would you recommend an early adopter/early majority SWE to pay particular attention to?
The emerging unification of Microservices and Streaming/Fast Data architectures. This includes both using Streaming/Fast Data to analyze large volumes of data in close to real time, getting value from data faster, as it arrives into the services endpoints, as well as bringing the power of Streaming into the Microservices themselves—both as a communication protocol as well as a persistence solution (through event logging)—including both client-to-service and service-to-service communication.
Similar Talks
Scaling DB Access for Billions of Queries Per Day @PayPal
Software Engineer @PayPal
Petrica Voicu
Psychologically Safe Process Evolution in a Flat Structure
Director of Software Development @Hunter_Ind
Christopher Lucian
PID Loops and the Art of Keeping Systems Stable
Senior Principal Engineer @awscloud
Colm MacCárthaigh
Are We Really Cloud-Native?
Director of Technology @Luminis_eu
Bert Ertman
The Trouble With Learning in Complex Systems
Senior Cloud Advocate @Microsoft
Jason Hand
How Did Things Go Right? Learning More From Incidents
Site Reliability Engineering @Netflix
Ryan Kitchens
What Breaks Our Systems: A Taxonomy of Black Swans
Site Reliability Engineer @Slack, Contributor to Seeking SRE, & SRECon Steering Committee
Laura Nolan
Cultivating High-Performing Teams in Hypergrowth
Chief Scientist @n26
Patrick Kua
Inside Job: How to Build Great Teams Within a Legacy Organization?
Engineering Director @Meetup