Microservice Architecture
Supported by KongThe FTGO application and the Database per service pattern
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:
ftgo-order-service:
build: ./ftgo-order-service
environment:
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
- Look at the FTGO application
- Read my Microservices patterns book
- Talk to me about my microservices consulting and training services.
- Learn more about microservices at adopt.microservices.io
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 workshops.
MICROSERVICES WORKSHOPS
Chris teaches comprehensive workshops for architects and developers that will enable 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.
Learn moreLEARN 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
Remote consulting session
Got a specific microservice architecture-related question? For example:
- Wondering whether your organization should adopt microservices?
- Want to know how to migrate your monolith to microservices?
- Facing a tricky microservice architecture design problem?
Consider signing up for a two hour, highly focussed, consulting session.
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 MECNPWNR to sign up for $120 (valid until May 16th, 2023). There are deeper discounts for buying multiple seats.
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.
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.
Join the microservices google group
Topics
Note: tagging is work-in-process
anti-patterns · application api · application architecture · architecting · architecture documentation · assemblage · beer · containers · dark energy and dark matter · deployment · design-time coupling · development · devops · docker · eventuate platform · glossary · hexagonal architecture · implementing commands · implementing queries · inter-service communication · kubernetes · loose coupling · microservice architecture · microservice chassis · microservices adoption · microservicesio updates · multi-architecture docker images · observability · pattern · refactoring to microservices · resilience · sagas · security · service api · service collaboration · service design · service discovery · service granularity · service template · software delivery metrics · success triangle · tacos · team topologies · transaction management · transactional messaging
