The FTGO application and the Database per service pattern

New public workshop: Architecting for fast, sustainable flow - enabling DevOps and Team Topologies thru architecture. Learn more and enroll.

One of the key characteristics of the microservice architecture is that each service’s data is private, e.g. the Database per Service pattern.

As the pattern points out, you aren’t required to have a separate database server for each service. Instead, multiple services can share the same database server with a logical separation of their data.

I’ve recently enhanced my book’s example application (FTGO) to properly demonstrate this pattern. Each service has database credentials that only grant it access its own (logical) database on a shared MySQL server.

Here, for example, is the configuration for the Order Service:

  build: ./ftgo-order-service
    SPRING_DATASOURCE_URL: jdbc:mysql://mysql/ftgo_order_service
    SPRING_DATASOURCE_USERNAME: ftgo_order_service_user
    SPRING_DATASOURCE_PASSWORD: ftgo_order_service_password

The ftgo_order_service_user/ftgo_order_service_password credentials only grant it access to the ftgo_order_service database:

CREATE USER 'ftgo_order_service_user'@'%' IDENTIFIED BY 'ftgo_order_service_password';
create database ftgo_order_service;
GRANT ALL PRIVILEGES ON ftgo_order_service.* TO 'ftgo_order_service_user'@'%';

The other services (Accounting Service, Consumer Service Kitchen Service, and Restaurant Service) have a similar configuration. The Order History Service, which implements a CQRS view, has its own DynamoDB tables.

To learn more

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

About is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action, the creator of the original, and the author of Microservices patterns.

New workshop: Architecting for fast, sustainable flow

Enabling DevOps and Team Topologies thru architecture

DevOps and Team topologies are vital for delivering the fast flow of changes that modern businesses need.

But they are insufficient. You also need an application architecture that supports fast, sustainable flow.

Learn more and register for my June 2024 online workshops....


I help organizations improve agility and competitiveness through better software architecture.

Learn more about my consulting engagements, and training workshops.

LEARN about microservices

Chris offers numerous other resources for learning the microservice architecture.

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

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 GIVLKECM to sign up for $145 (valid until June 19th, 2024). There are deeper discounts for buying multiple seats.

Learn more

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.

Signup for the newsletter

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 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.

Join the microservices google group