IBM

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.

Continue reading

LB0105EN

Infrastructure

393 Enrolled
(15)

At a Glance

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

Course Staff

Wade Waldron

Wade Waldron

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.

Estimated Effort

6 hours

Level

Beginner

Language

English

Tell Your Friends!

Saved this page to your clipboard!