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.
Zero downtime migrations
From the course: Software Architecture: Breaking a Monolith into Microservices
Zero downtime migrations
- [Instructor] The business made pretty clear that this whole initiative that is planned must not mean that the application has to be taken down. After all the money's made with conversions and the minute downtime can be directly measured in dollars. But being a good architect, you also want to provide a migration past that doesn't mean a complete outage. Also you want to be able to abort the migration at any point in time. It's either all or nothing. And if something fails, the application should not end up in a chaotic, half migrated state. So how can we accomplish this? First, we have to prepare the monolith and add the new functionality needed. So you will tell the responsible team to implement the service proxy methods part and here comes the important part. This new functionality should be hidden behind the feature toggle. These are programmatic switches that can be turned on or off during runtime. Technically,…
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)
-
-