From the course: Software Architecture Foundations
Join today to access over 22,600 courses taught by industry experts or purchase this course individually.
Reactive and choreographed systems
From the course: Software Architecture Foundations
Reactive and choreographed systems
- Let's finish up with one final pattern, reactive architectures. This one is another example of how patterns intermingle because microservices are often built as reactive systems. Most of our work is in declarative or orchestrated systems. For example, a normal set of method calls is a declarative system. You declare that some other object does something, and then you usually wait around for the result. Here's an example of a simple declarative approach in a microservice context. The shopping-cart service asks the billing, warehouse, and email services to do something for it. The expectation is that each of these requests are processed in sequence and that each one will succeed. Declarative systems don't have to be synchronous, you can have some operations going on in parallel, but they usually are. It turns out that this declarative approach does not work very well. First, the shopping-cart service is tightly coupled to the services it talks to. If anything in any of those services…
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.