Building resilience into applications and architecture grows increasingly more complex with the modern demands of day-to-day business. This course will teach you how to apply the foundational principles of reactive systems to meet these demands.
In an effort to stem the increasing complexity of building resilience into modern day applications and architecture, this course, Building Reactive Microservices, covers the design and implementation of failure-tolerant microservices. You’ll learn design principles common to microservice architectures. You’ll also discover industry-proven best practices for building reactive applications, including event sourcing, idempotency, commutative messaging, and distributed transactions using SAGAs. Whether migrating toward microservices or seeking to improve upon what you currently have, at the end of this course you will have a proven set of skills for designing, developing, and/or improving the microservices currently under your influence.
Matthew Alexander is a Software Engineer with years of practical experience building distributed systems in the AWS cloud. In his current capacity he leads the charge in designing and implementing next generation infrastructure for Lucid Software, Inc. Prior to working for Lucid, he was instrumental in designing and bringing to life several of AWS' external and internal product offerings for Cloudfront ([email protected]) and S3.
Course Overview Hi, my name is Matthew Alexander, and welcome to my course, Building Reactive Microservices. I'm a software engineer at Ancestry.com where my forte is creating distributed systems using reactive system principles. With the increasing demands placed upon businesses ranging from GDPR, strong customer adoption, or increased security constraints, building resilience into applications and architecture grows increasingly more complex. In this course, we will cover the design and implementation of failure‑tolerant microservices using reactive system principles. Some of the major concepts we will cover include events sourcing, idempotency, commutative messaging, and distributed transactions using sagas. Whether migrating toward microservices or seeking to improve what you currently have, at the end of this course, you will have a foundational skill set for designing and developing resilient, responsive, elastic, and message‑driven applications that are able to deal with the modern demands of business. I hope that you'll join me as we seek to strengthen some of the foundational principles of building durable microservices with the Building Reactive Microservices course, at Pluralsight.