- [Instructor] This course is about microservices,
and the scenario we will look at is a pretty common one.
We have an existing app
that wasn't created with microservices in mind,
and now we want to split it up into services.
I covered the possible reasons for that already.
The app we're splitting apart,
is the conference app we just set up.
And as you saw,
it basically consists of three conceptual parts.
The main application that does all the heavy lifting
and template rendering, content related to speakers,
and content relating to displaying and posting feedback.
We now decided that we want all those components
to be entities on their own.
So we will move out the functionality into microservices.
In between we will add a service registry
that will know where to find those services
in our infrastructure
and that will also provide some load balancing.
Additionally, we will add a communication layer
to the main application
that will provide some resilience against outages.
This will be achieved by circuit breaking and caching.
Finally, we will add an additional level of abstraction
by using a queue to send feedbacks through it
instead of posting data directly to the respective services.