From the course: Software Architecture: Breaking a Monolith into Microservices
Unlock the full course today
Join today to access over 22,600 courses taught by industry experts or purchase this course individually.
Making the final step
From the course: Software Architecture: Breaking a Monolith into Microservices
Making the final step
- [Instructor] It would be out of scope and does not provide much failure to show the migration for each and every capability of our monolith. By now, you should have a good understanding about the underlying technical concepts of such migrations. I also did not cover how to orchestrate services, like with Kubernetes. There are dedicated courses for this. What we're left now with is the skeleton of the monolith, pretty much. Models and persistence layer are gone and all of control functionality and business logic is now proxy to the respective services, the so-called API gateway, which is usually provided by the service orchestration you're using. It basically routes your request to the respective service, or if services are redundant, to a service instance using load balancing. A redesign of the website is now relatively easy, as all business logic has been moved out into services that can be developed quickly and…
Contents
-
-
-
-
(Locked)
Design mistakes and how to avoid them5m 13s
-
(Locked)
Refactor or rewrite?1m 56s
-
(Locked)
Choosing your first migration target1m 53s
-
(Locked)
Splitting out your first service3m 21s
-
(Locked)
Zero downtime migrations3m 37s
-
(Locked)
Migrating interdependent, complex capabilities4m 5s
-
(Locked)
Providing a migration API layer1m 23s
-
(Locked)
What about the front end?4m 27s
-
(Locked)
Making the final step2m 22s
-
(Locked)
-
-