Reactive Architecture: Reactive Microservices

When we use the term Reactive, we are usually talking about Reactive Microservices. But what is a microservice? And how can we make it Reactive? This course will explore the difference between monoliths and microservices and show the journey to making a system Reactive.

About This Course
When we use the term Reactive, we are usually talking about Reactive Microservices. But what is a microservice? And how can we make it Reactive? This course will explore the difference between monoliths and microservices and show the journey to making a system Reactive.

What will I get after passing this course?
You will receive a completion certificate.
Course Syllabus
The Software Spectrum
An introduction the Monolith to Microservices sprectrum
The bascis of choosing between a Monolith or Microservice software approach
Monoliths
Some Monoliths can be Big Balls of Mud
Characteristics of Monoliths
Advantages and Disadvantages of Monoliths
Microservices
Service Oriented Architecture
Characteristics of Microservices
Responsibilities of Microservices
Advantages and Disadvantages of Microservices
Decomposing a Monolith into Microservices
Principles of Isolation
State, Space, Time and Failure
Monoliths and the Principles of Isolation
Microservices and the Principles of Isolation
Isolation Techniques
Bulkheading
Circuit Breakers
Message Driven Architecture
Autonomy
Gateway Services
General Information
This course is self-paced.
It can be taken at any time.
It can be taken as many times as you wish.
Recommended skills prior to taking this course
Experience in the design of software systems.
Grading scheme
The minimum passing mark for the course is 75%, where the review questions are worth 40%, the case study exercises are worth 30% and the final exam is worth 30% of the course mark.
You have 1 attempt to take the final exam with multiple attempts per question.
Requirements
You should either understand all the concepts or have taken Reactive Architecture: Introduction to Reactive Systems and Reactive Architecture: Domain Driven Design