Architecture Presentation

1. Luu Thanh Sang
BUILDING MONOLITHIC APPLICATION AND
MODULATION ACCORDING TO THE PRINCIPLES
OF MICROSERVICES

2. About me
Software Architect at Getfly CRM
LUU THANH SANG

3. What is Microservices?
An architectural style
Collection of Loosely-Coupled Services with the ability to deploy
independently (process, database)
Inter-services communicate with each other through network
protocol

4. Why Microservices?
1. Modular
2. Deploy, Monitor and scale
independently between services
3. Developing independently
between teams
4. Improves the source code
security

5. Difficulties
1. Difficult to operate, detect and handle errors
2. Need to implement communication
mechanisms between Inter-Services
3. Eventual Consistency
4. Network latency

6. An architectural style
Modular Monolithic Collection of Loosely-Coupled
Modules with the ability to
deploy independently (database)
Modules communicate with each
other through network protocol
or in-process
Independent Internal Architecture
(according to microservice's principles)

7. Module Definition
Definition of scope (business capability, bounded context)
Each module owns its own database
Single responsibility principle (SRP)
Each module owns its own API Interfaces
Each module decides on the Internal architecture itself
Shared Code Base (Framework, Infrastructure components...)
Split source code (each module manage its own source code by using git submodule)

8. Multi-Architecture
User
Aggregate
Role
Entity
DTO
DDD Simple CRUD
User Module

9. Internal Pub-Sub system
Ordering Module
(Publisher)
Inventory Module
(Subscriber)
OrderCreated
(Domain Event)
(Event Driven Architecture)

10. Internal Pub-Sub system
composer require symfony/event-dispatcher

11. Inventory
Module
Transaction
Local transaction
warehouse A warehouse B
goods issue goods receipt

12. Inventory
Module
Transaction
Distributed Transaction
Ordering
Module
Local transaction Local transaction

13. Inventory
Module
Ordering
Module
Transaction
Distributed Transaction
Saga Pattern (Choreography)
Local transaction
Local transaction
Create Goods Issue Command
order events channel
inventory events channel
InventoryOutOfStock
GoodsIssueCreated
Domain Event
OrderCreated
Domain Event
Approve Order Command

14. Transaction
Distributed Transaction
Saga
Two phase commit
Three phase commit

15. Inventory
Module
(DDD)
User
Module
Ordering
Module
(DDD)
Role
(CRUD)
User
(DDD)
API API API
Modular Monolithic Overview
Framework
Internal Pub-sub system
DB
DB
DB

16. App
Horizontal Scaling
App App App
scaling out...

17. Conclusion
The most important thing to succeed the modular monolithic is the way we divide
the module
The system becomes a Distributed System when we separate the database for each
module
Event Driven Architecture keeps the boundaries clear between the modules

18. Thank you!
fb.com/sang.aug