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.
Splitting out your first service
From the course: Software Architecture: Breaking a Monolith into Microservices
Splitting out your first service
- The authentication capability is the perfect service to move out, and you're now on the drawing board to provide guidance to the developers that will lead to implement it. First, we have to have a closer look at the functionality provided by the user controller in our monolith. And there are a few actions that we didn't show before but are related to authentication. First there authenticate action of course. This is needed to do the authentication with username and password. But there's also the profile management that we need to look into. When a user creates a new profile, they also provide their username which is the email address and the password. So this needs to somehow be connected to the service which should own all the data related to authentication in the future. Also, profiles can be updated and along with the user information, the email and the password can be changed as well. Additionally, profiles can…
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)
-
-