This document discusses microservices architecture and Docker. It begins with an overview of monolithic versus microservices approaches. Key lessons learned with microservices include bounded context, service communication using external requests, internal requests, and message queues. Other topics covered include centralized configuration, request logging, service monitoring, service discovery, distributed transactions, and deployment using Docker. Docker is introduced as a way to containerize microservices for scalability, reliability and portability.

1. Microservices
& Docker
Võ Duy Tuấn
CEO/Founder
Teamcrop.com

2. • Monolithic vs Microservices
• Lesson learned
• Docker for microservices
Table of contents

3. 1. Monolithic
A
B
C
Once upon a time…
DB

4. 1. Monolithic (cont.)
A
B
C
1 year later…
DB
D
M
H
L
K
G
I
E
F
J

5. 1. Monolithic (cont.)
2 years later…
DB
(Master)
DBDB
(Slave)
Replicate
Load
Balancer

6. 1. Monolithic (cont.)
3 years later…
DB
(Master)
DBDB
(Slave)
Replicate
Load
Balancer
DB
(Master)
DB
(Slave)DB
(Slave)DB
(Slave)DB
(Slave)
OH MY GOD!

7. 2. Microservices
A
B
C
Once upon a time…
DB1
Load
Balancer
DB2
DB3

8. 2. Microservices (cont.)
A
B
C
1 year later…
D
G
H
E
K M
J
L
I F
Load
Balancer
DB1
DB2
DB3
DB4
DB5
OH MY GOD!
A

9. DB1
(Slave)
2. Microservices (cont.)
A
2 years later…
Load
Balancer
DB1
(Master)AA
Replicate
…
…
…
…

10. DB1
(Slave)
2. Microservices (cont.)
A
3 years later…
Load
Balancer
DB1
(Master)
AA
Replicate
…
…
…
…
AAA
DB1
(Slave)
DB1
(Slave)
DB1
(Slave)
DB1
(Master)

11. 3. Summary of long term grow
MONOLITHIC MICROSERVICES

12. Lesson Learned

13. 1. Bounded context

14. 1. Bounded context (cont.)

15. 2. Service Communication
• External request
• Internal request
• Message Queue

16. 2.1. External request
Service X
3rd-party
system • JSON Web Token
(JWT):
o Expiration
o Blacklist
o Size
o CORS policy (ajax)
• Restful WS
• Rate Limit

17. 2.2. Internal request
Service X
• Access Trusted
Network:
o Key exchange
o Overhead
o Monitor
o Fail in the middle
o Timeout
o SDK
o Request type:
o Fire & Wait
o Fire & Forget
Service Y

18. 2.3. Message Queue
Service X
• Service Bus:
o Pub/Sub
o Ack
o Retry
o Delay
o Load Balancer
o Consumer HA
Service Z
Call X Call Y Call X Call A
Call X Broker
Call X
Call X Call Y
Job Queue (Ex: RabbitMQ)

19. 3. Centralized Configuration

20. 4. Request Log

21. 5. Service Monitoring
status.teamcrop.com

22. 6. Service discovery

23. OPS / Service discovery
(cont.)

24. 6. Service discovery (cont.)
HAProxy
Consul-template
Docker Engine
Backend 01 : Port 32680
Backend 02 : Port 32681
Backend 03 : Port 32682
Update haproxy.cfg
& Reload haproxy
CONSUL REGISTRATOR
Notify
Update
Pull
1
2
3
4
5
Client
gliderlabs/registratorgliderlabs/consul-server

25. 7. Distributed Transaction
T: Transaction
C: Compensation (Undo)
Learn more: http://kellabyte.com/2012/05/30/clarifying-the-saga-pattern/
SAGA Pattern

26. 8. Deployment

27. Docker for
Microservices

28. 1. What is Docker?

29. 2. Docker container in real

30. 3. Docker container stats
> docker stats $(docker ps --format '{{.Names}}')

31. 4. Docker RUN example
docker run -ti -d
-h tc-notify
--restart=always
--name tc-notify-$RANDOM -p :80
-e SERVICE_TAGS=tc-notify
-e SERVICE_NAME=tc-microx
-e CONFIG_URL=http://configurl.com/?abc
-e LOG_IP=127.0.0.1
-v /data/logs/tc-notify:/var/www/log
teamcropregistry.com/teamcrop/tc-notify

32. 5. Docker UI - Rancher

33. Thanks!
CONTACT:
tuanmaster2012@gmail.com
0938 916 902
teamcrop.com