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.

Signup for the newsletter

LEARN about microservices

Chris offers numerous resources for learning the microservice architecture.

Training classes

Chris teaches comprehensive workshops and training classes for executives, architectures 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.

Get the book: Microservice 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

Ready to start using the microservice architecture?

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

Assess your application's microservice architecture and identify what needs to be improved.

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

Extracting the Delivery Service - Step 2, Split the database

The previous post described the first step of the refactoring process, which consisted of moving the delivery management code into its own ftgo-delivery-service module. It left the database unchanged and the newly defined JPA @Entity classes in the ftgo-delivery-service module were mapped to the existing database tables. The Delivery entity was mapped to the Order entity’s ORDERS table.

The second step of the refactoring process splits the database and defines a separate ftgo_delivery_service database for the ftgo-delivery-service module. The following diagram shows the resulting structure:

The changes are primarily in this Git commit.

About the database migrations

The following Flyway-based schema migrations in ftgo-flyway/src/main/resources/db/migration transform the database:

  • V2__split_courier.sql
  • V3__replica_restaurant.sql
  • V4__extract_into_delivery.sql
  • V5__FK_constraints.sql

These migrations create the tables in the ftgo_delivery_service database and populate them with data from the monolith’s ftgo database. They also define triggers, which replicate data between the two databases. Some triggers replicate updates to data owned by the FTGO monolith, such as Couriers and Restaurants, to ftgo-delivery-service module’s database. The other triggers replicate changes to data owned by the ftgo-delivery-service module to the monolith’s database in order to make it accessed by the read-only columns described in the previous post. For example, when the ftgo-delivery-service updates Courier.availability a trigger updates the corresponding column in the ftgo database. Let’s take a look at each of these schemas.


This migration defines the courier and courier_actions tables in the ftgo_delivery_service database and populates them with data from the ftgo.courier and ftgo.courier_actions tables. It defines several triggers that synchronize data between the two schemas.

The first two replicate changes made to the ftgo_delivery_service database to the ftgo database:

  • ftgo_delivery_service.courier_availability_updated - replicates ftgo_delivery_service.courier.available to ftgo.courier.available
  • ftgo_delivery_service.courier_actions_created - replicates inserts into ftgo_delivery_service.courier_actions to ftgo.courier.courier_actions (TODO what about deletes)

The other two triggers replicate changes made to the ftgo database to the ftgo_delivery_service database:

  • ftgo.courier_created - replicates inserts into ftgo.courier to ftgo_delivery_service.courier
  • ftgo.courier_updated - replicates updates of ftgo.courier to ftgo_delivery_service.courier


This migration defines the restaurant table in the ftgo_delivery_service database and populates it with restaurants from ftgo.restaurant. It also defines a trigger that replicates inserts into ftgo.restaurant table to the ftgo_delivery_service.restaurant table.

TODO what about UDs


This migration defines the delivery table in the ftgo_delivery_service database and populates it with deliveries from ftgo.delivery. It also defines a trigger that replicates updates of the ftgo_delivery_service.assigned_courier_id column to the ftgo.delivery table.


This migration creates foreign key constraints between the newly defined tables.

About the code changes

In addition to the schema changes, there are a few code changes. First, the JPA entities in the ftgo-delivery-module are mapped to new databases tables. For example, Delivery is mapped to the delivery table:

@Table(name = "delivery", catalog = "ftgo_delivery_service")
public class Delivery {

Second, the DeliveryState enum is simplified since it no longer needs to mirror OrderState. It now just defines values that correspond to the state of the Delivery.

Third, because Delivery no longer shares a table with Order the DeliveryService.scheduleDelivery() method can no longer load the Delivery. Instead, it must create the Delivery:

public class DeliveryServiceImpl implements DeliveryService, DeliveryCourierService {

  private DeliveryRepository deliveryRepository;

  public void scheduleDelivery(LocalDateTime readyBy, Long orderId, long restaurantId, Address deliveryAddress) {
     delivery = deliveryRepository.save(delivery);

What’s next

Copyright © 2019 Chris Richardson • All rights reserved • Supported by Kong.