This document outlines a microservices delivery pipeline from development to production using .NET Core, Docker, and AWS. It describes deploying microservices through continuous integration and delivery pipelines. Key aspects include using Docker containers and container orchestration with ECS for zero-downtime deployments. Infrastructure is provisioned and managed as code using tools like CloudFormation. The pipeline supports hotfixes and rolling back changes when issues arise.

1. Microservices delivery pipeline with
.NET Core, Docker and AWS
Oleksandr Nahirniak
EPAM Systems

2. Goals of presentation
• Show delivery pipeline of microservices from developer machine to
production
• Demonstrate efficient way to deploy your infrastructure around the services
• Show techniques that we use for successfully deployment our microservices
2

3. INTRO

4. Who we are?
• What are merge and acquisition?
• How did it work earlier?
• What do we solve?
• Startup for the customer?
4

5. What do we use?
- Timmy, where are
my containers?!
- What’s up guys?
- Keep calm, Johnny,
here they are.
-UPDATE_IN_PROGRESS

6. How big we are?
• We have 4 environments
• 46 microservices per environment
• 107 running instances
• 16 databases in one RDS cluster
• 20+ GB logs per month
• 30+ message queues
• 14 lambda functions

7. DELIVERY EVOLUTION

8. Old way of delivery
8

9. Old way of delivery
9

10. Old way of delivery
10

11. Old way of delivery
11

12. Old way of delivery
12

13. Old way of delivery
13
-HEY! I NEED ONE MORE
ENV!

14. Old way of delivery
14
-HEY! I NEED ONE MORE
ENV!

15. New way of delivery
image
IMAGE
STORAGE

16. New way of delivery
image
IMAGE
STORAGE

17. New way of delivery
17
image

18. New way of delivery
18
image
container
container
container
…

19. New way of delivery
19
image
container
container
container
…
-HEY! I NEED ONE MORE
ENV!

20. New way of delivery
20
UATprod
- NO PROBLEM!

21. OUR DELIVERY WAY

22. Delivery strategies & concepts
• What are artifacts?
• Service deployment
• Infrastructure deployment
• Service interaction
• Summary
• F*ckups

23. What are artifacts?

24. SERVICE DEPLOYMENT

25. Delivery strategy
dev staging
(code)git push
prodUAT
- development

26. Delivery strategy
dev staging
(code)git push
UAT prod
- development
- release

27. Delivery strategy
dev staging UAT prod
(code)git push
- development
- release

28. Delivery strategy
dev staging UAT prod
(code)git push
- development
- release

29. HOTFIXES

30. Hotfix strategy
dev staging UAT prod
- development
- release
(code)git push

31. Hotfix strategy
dev staging UAT prod
- development
- release
(code)git push

32. Hotfix strategy
dev staging UAT prod
- development
- release
(code)git push
- hotfix

33. Hotfix strategy
dev staging UAT prod
- development
- release
(code)git push
- hotfix

34. Hotfix strategy
dev staging UAT prod
- development
- release
(code)git push
- hotfix

35. ZERO-DOWNTIME DEPLOYMENT

36. Zero-downtime deployment
• Start with blue service composed of a task
definition and ALB
• Create new task definition based on new version
of Docker image
• Create green service with new task definition
and map to existing ALB
• Scale up green service by incrementing number
of tasks
• Decommission blue service by setting task count
to 0
D E P L O Y M E N T P R O C E S S :
36
container
container
container
Load balancer
ECS Cluster

37. Zero-downtime deployment
• Start with blue service composed of a task
definition and ALB
• Create new task definition based on new version
of Docker image
• Create green service with new task definition
and map to existing ALB
• Scale up green service by incrementing number
of tasks
• Decommission blue service by setting task count
to 0
D E P L O Y M E N T P R O C E S S :
37
container
container
container
container
Load balancer
ECS Cluster

38. Zero-downtime deployment
• Start with blue service composed of a task
definition and ALB
• Create new task definition based on new version
of Docker image
• Create green service with new task definition
and map to existing ALB
• Scale up green service by incrementing number
of tasks
• Decommission blue service by setting task count
to 0
D E P L O Y M E N T P R O C E S S :
38
container
container
container
container
container
container
Load balancer
ECS Cluster

39. Zero-downtime deployment
• Start with blue service composed of a task
definition and ALB
• Create new task definition based on new version
of Docker image
• Create green service with new task definition
and map to existing ALB
• Scale up green service by incrementing number
of tasks
• Decommission blue service by setting task
count to 0
D E P L O Y M E N T P R O C E S S :
39
container
container
container
container
container
container
stopped
stopped
stopped
Load balancer
ECS Cluster

40. INFRASTRUCTURE DEPLOYMENT

41. Problem statement
dev staging UAT prod

42. Problem statement
dev staging UAT prod

43. Problem statement
dev staging UAT prod
V2 V2V2

44. Problem statement
dev staging UAT prod
V3 V3V2 V2

45. Problem statement
dev staging UAT prod
V4 V3V2 V2

46. Infrastructure as a code
dev/staging/UAT/prod

47. Infrastructure as a code

48. Infrastructure as a code

49. Infrastructure as a code
CONFIDENTIAL | © 2019 EPAM Systems, Inc.

50. SERVICE INTERACTION

51. Service interaction
Users Documents
GET

52. Service interaction
Documents
Client

53. Service interaction
Users Documents Notifications
Client
Client
Client

54. Service interaction
Users Documents Notifications
WebBFF MobileBFF
Internet
GET
POST
MESSAGE
MESSAGEGET

55. Summary
55
• Don’t afraid to use .NET Core with Linux
• Unify your artifacts and minimize their count
• Use tools for provisioning and configuration management yours
apps(carefully)

56. F*ckups
56
• Classical pitfall with removing database column
• Return infrastructure to the 3 months earlier state
• Shutting down of whole ECS cluster

57. THE END