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.

Providing a migration API layer

Providing a migration API layer

From the course: Software Architecture: Breaking a Monolith into Microservices

Start my 1-month free trial

Providing a migration API layer

“

- [Instructor] I said before that the service should not court back into the monolith, and this is still true. But there may be situations when a service needs information that is not yet available through another service, but instead still stored somewhere deep in the monolith. So we need a way to get this data, but we also want to do it in a controlled way and not maybe just make the database readable through the web. Ideally we need an end point that is identical to what the service would need to provide. So if we look back at our virtual example from before, this would be when we would get together with the monolith team and asked them to expose a bell security API to the web. Ideally we could already tell them all in points we would need going forward. For the watch list, we would need an end point that returns to notification preferences for a given user. Now our notify watcher service can call back home to…

Contents