About This Course
This course teaches the core principles behind Reactive Architecture. It introduces students to why we need Reactive Systems, and what problems they are trying to solve. It also contrasts Reactive Architectures with Reactive Programming, showing how they relate, and how they are different.
- Why Reactive
- What is the problem that Reactive Architecture is attempting to solve?
- How does unresponsive software impact it's users?
- What is the goal of Reactive Architecture?
- Reactive Principles
- An introduction to the Reactive Manifesto
- An explanation of the Reactive Principles
- Reactive Systems vs Reactive Programming
- What are Reactive Systems?
- What is Reactive Programming?
- How are Reactive Systems related to Reactive Programming?
- The Actor Model and it's relationship to Reactive Systems.
- Case Study: Reactive BBQ
- An analysis of a specific case study
What will I get after passing this course?
- You will receive a certificate of course completion.
Recommended skills prior to taking this course
- Some experience in the design of software systems is ideal but not required
Wade Waldron is the Microservices Practice Lead, Senior Training Developer, and Senior Consultant at Lightbend. He is the primary author of the Lightbend Reactive Architecture training course.
Wade started his career as a developer in 2005 building games for the Playstation 2, Xbox, etc. In 2011 he joined Point2 Homes where he began working on an Akka based microservices platform to provide realtime updates to real estate websites. In 2014 Wade joined BoldRadius where he consulted with a variety of companies on how to use Akka, and related technologies. He also began teaching courses on Akka and Scala.
In 2016, Wade released a book "Applied Akka Patterns" along with his co-author Michael Nash
Today Wade works with Lightbend where he consults with clients and builds training materials. He focuses on helping people make a smooth transition from a monolithic application to Reactive microservices.