Microservice Architecture
Supported by KongExtracting the Delivery Service - Step 5, Removing obsolete code from the monolith
This article describes the fifth step in the process of extracting the Delivery Service from the FTGO application monolith.
The previous articles are as follows:
- About the FTGO monolith
- Step 1: Split the code
- Step 2: Split database
- Step 3: Create and deploy the
Delivery Service - Step 4: Use the
Delivery Service
After step 4, the Delivery Service manages deliveries.
The fifth step is to remove the now obsolete delivery management code from the FTGO application.
This change is actually quite simple. The two main changes we need make are
- remove
ftgo-delivery-backendmodule as a dependency - remove the
@Configurationclass that@Importsclasses from that module
There are also a few other minor changes, such as renaming a build script.
Module structure
The following diagram shows the new module structure:
The key change is that the ftgo-delivery-service-proxy module no longer depends on the ftgo-delivery-backend module.
Git commits
These changes are in the extract-delivery-service-05-delete-old-code branch and consist of a single commit
What’s next
- Look at the FTGO monolithic application code
- Read chapter 13 of my book Microservices patterns, which covers refactoring to microservices
- Talk to me about my microservices consulting and training services
About Microservices.io
Microservices.io is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action, the creator of the original CloudFoundry.com, and the author of Microservices patterns.
Chris helps clients around the world adopt the microservice architecture through consulting engagements, and training classes and workshops.
Learn how to create a service template and microservice chassis
Take a look at my Manning LiveProject that teaches you how to develop a service template and microservice chassis.
New virtual bootcamp: Distributed data patterns in a microservice architecture
My virtual bootcamp, distributed data patterns in a microservice architecture, is now open for enrollment!
It covers the key distributed data management patterns including Saga, API Composition, and CQRS.
It consists of video lectures, code labs, and a weekly ask-me-anything video conference repeated in multiple timezones.
The regular price is $395/person but use coupon WSSEULWL to sign up for $190 (valid until November 30th, 2022). There are deeper discounts for buying multiple seats.
LEARN about microservices
Chris offers numerous resources for learning the microservice architecture.
Training classes
Chris teaches comprehensive workshops, training classes and bootcamps for executives, architects and developers to help your organization use microservices effectively.
Avoid the pitfalls of adopting microservices and learn essential topics, such as service decomposition and design and how to refactor a monolith to microservices.
Delivered in-person and remotely.
Get the book: Microservices Patterns
Read Chris Richardson's book:
Example microservices applications
Want to see an example? Check out Chris Richardson's example applications. See code
BUILD microservices
Consulting services
Engage Chris to create a microservices adoption roadmap and help you define your microservice architecture,
The Eventuate platform
Use the Eventuate.io platform to tackle distributed data management challenges in your microservices architecture.
Eventuate is Chris's latest startup. It makes it easy to use the Saga pattern to manage transactions and the CQRS pattern to implement queries.
ASSESS your architecture
Consulting services
Engage Chris to conduct an architectural assessment.
Self assessment
Alternatively, conduct a self-assessment using the Microservices Assessment Platform.
Join the microservices google group
