About this Workshop
Designing Reactive systems and microservices requires architects and teams to think differently about design - taking into account concurrency, messaging and coordination - in order to achieve the promise of resilient and elastic software. As microservices have emerged as the gold standard of developing modern software applications, every team needs to develop a deep understanding of how to design, build and operate software in a Reactive world if they want to remain relevant.
The Lightbend Reactive Architecture course teaches teams - from development managers to architects to software developers - how to think about and leverage Reactive architectures from design through to production operations.
The certified Lightbend course presents a series of architectural exercises. Students will work in groups to address problems and design solutions. The exercises are completed without the use of code. This allows the course to appeal to a broad audience.
- Build the confidence to design and deploy scalable, resilient, responsive and elastic systems
- Certified Lightbend Trainers share best practices for designing Reactive microservices
- Reactive techniques and patterns
- Developers and Architects looking to develop Reactive systems
- Architects with an interest in Domain Driven Design and related architectural patterns
- Managers and Team Leads looking for elasticity, resilience and scale in their products and systems
- Why Reactive
Domain Driven Design
- Reactive Manifesto
- Reactive Principles
- Reactive Systems
- Reactive Programming
- Actor Model
- Ubiquitous Language
- Bounded Contexts
- Anti-Corruption Layers
- Command, Events, Queries
- Value Objects, Entities, Aggregates
- Services, Factories, Repositories
- Hexagonal Architecture
Consistency, Availability, Scalability
- Microservices vs Monoliths
- Isolation of State, Space, Time, Failure
- Circuit Breakers
- Gateway Services
Messaging and Coordination
- Performance vs Scalability
- Strong Consistency vs Eventual Consistency
- Contention and Amdahl's Law
- Coherency and Gunther's Law
- Synchronous vs Asynchronous Messaging
- Saga Pattern
- Two Generals Problem
- Delivery Guarantees
- Point to Point
- Audit Logs
- Event Sourcing
- Command Sourcing
- Consistency, Availability, Scalability in CQRS
Intermediate - practical experience in software development and analysis is assumed
Three days - 21 hours of classroom time, plus breaks
Extensive design and discussion - students design a Reactive application, analyzing a sample domain, and contrasting it with a monolithic application design
Students must bring their own laptops. Pen, paper, sticky notes and whiteboards are assets for exercise work.
Related Blog Post
Introducing A New Remote/Onsite Training Course
To Help Development Teams Learn Reactive Architectures
Director, Enterprise Support, Lightbend, Inc.
Zac has a passion for technology, with a career that includes working with Steve Jobs at NeXT Computer, and drives him to stay abreast of emerging technologies. As Director of Enterprise Support, Zac is responsible to developing best practices and enabling Lightbend clients to achieve their “Happy Path” — Enterprise-wide Reactive success stories.
Zac is a Microservices systems architect with a deep understanding of Reactive Architecture. He’s a passionate teacher of Scala, Reactive Architecture, functional programming, and an adept agile coach. Formerly, he led Accenture’s Scala practice, has worked in the defense industry, and co-founded several Silicon Valley startups.
SHARE THIS WORKSHOP