YouTube: https://www.youtube.com/watch?v=CEF4FuwTvew&list=PLnKL6-WWWE_VNp6tUznu7Ca8hBF8yjKj2&index=55

1. MICROSERVICES DEPLOYMENT
ON-PREMISE AND IN AMAZON
WEB SERVICES
KAROL JUNDE
Network Solutions Architect

3. AGENDA
1. MICROSERVICES – BUZZWORD OR SOMETHING DEEPER
2. 12-FORM FACTOR APPLICATION
3. APP CONTAINERS
4. CI/CD PIPELINE – REMOVE WASTE DON’T CUT THE COSTS
5. MANTL/SHIPPED – PIPELINE ON PREM
6. CI/CD IN AWS
7. FIN/ACK

5. 1. MICROSERVICES – BUZZWORD OR SOMETHING DEEPER
2. 12-FORM FACTOR APPLICATION
3. APP CONTAINERS
4. CI/CD PIPELINE – REMOVE WASTE DON’T CUT THE COSTS
5. MANTL/SHIPPED – PIPELINE ON PREM
6. CI/CD IN AWS
7. FIN/ACK
AGENDA

6. MICROSERVICES
– BUZZWORD OR SOMETHING DEEPER

7. 1. CODE COMPLEXITY AND MAINTAINABILITY
2. DEPLOYMENT BECOMES THE TECHNOLOGY BOTTLENECK
3. FEAR TO CHANGE
4. LACK OF OWNERSHIP
5. FAILURE DEPENDENCIES
6. ONE SIZE DOESN’T FIT ALL (EX: RELATIONAL DB)
7. HARD TO SCALE OUT
PROBLEMS

9. „CLUSTER MANAGER” INSTEAD OF IT

10. THE ONLY DEPENDENCY THESE CODE BASES
HAVE ON ONE ANOTHER IS THEIR API
PREFER POLYGLOT OVER SINGLE STACK!!!!!
NUMEROUS SMALLER CODE BASES MANAGED
BY SMALL TEAMS

11. 1. REQUIREMENTS
2. QUALITY
3. DEPLOYMENT
4. SOURCE CODE
5. TECHNOLOGY SELECTION
TEAMS OWN
THEIR SERVICES

12. 1. THE SAME LOGGING TOOL
2. SERVICE BEHAVIOUR
3. INTEGRATION
4. METHOD OF DOWNSTREAM COMMUNICATION
5. MAYBE CONSIDER SERVICE TEMPLATES
RELEASE
AVOID BLACKHOLE

13. Two Pizza Rule
if a team can’t be fed by two pizzas
then it is too big
― Jeff Bezos

14. SERVICE ALLOW FOR INDEPENDENT
AXES OF SCALING
INDEPENDENT FAILURE DOMAINS = YOUR TEAM WORRIES
ABOUT DOWNSTREAM TEAMS DON’T BREAK

15. AVOID CASCADING
1. A MINOR SYSTEM FAILS
2. DEPENDENT SYSTEMS QUEUE WAITING FOR RESPONSE
FROM THE FAILED SYSTEM
3. DEPENDENCIES CASCADE
4. THE WHOLE SYSTEM FALLS OVER
FAILURES

16. BIND COMPONENTS AT RUN TIME

23. 1. FREEDOM OF CHOICE
2. LOW IMPACT SCHEMA
CHANGES
3. INDEPENDENT
SCALABILITY

26. adrianco / spigo
https://github.com/adrianco/spigo

27. 1. MICROSERVICES – BUZZWORD OR SOMETHING DEEPER
2. 12-FORM FACTOR APPLICATION
3. APP CONTAINERS
4. CI/CD PIPELINE – REMOVE WASTE DON’T CUT THE COSTS
5. MANTL/SHIPPED – PIPELINE ON PREM
6. CI/CD IN AWS
7. FIN/ACK
AGENDA

28. 12-FORM
FACTOR APPLICATION

30. I. CODEBASE
II. DEPENDENCIES
III. CONFIG
IV. BACKING SERVICES
V. BUILD, RELEASE, RUN
VI. PROCESSES
VII. PORT BINDING
VIII. CONCURRENCY
IX. DISPOSABILITY
X. DEV/PROD PARITY
XI. LOGS
XII. ADMIN PROCESSES

31. 1. MICROSERVICES – BUZZWORD OR SOMETHING DEEPER
2. 12-FORM FACTOR APPLICATION
3. APP CONTAINERS
4. CI/CD PIPELINE – REMOVE WASTE DON’T CUT THE COSTS
5. MANTL/SHIPPED – PIPELINE ON PREM
6. CI/CD IN AWS
7. FIN/ACK
AGENDA

32. APP CONTAINERS

33. „Container = sandbox environment
layered on the top of host OS”
CONTAINER != MICROSERVICE

34. 1. WHEN A DOCKER CONTAINER IS LAUNCHED, IT RUNS A SINGLE PROCESS.
THIS PROCESS IS USUALLY THE ONE THAT RUNS YOUR APPLICATION
WHEN YOU CREATE CONTAINERS PER APPLICATION
2. DOCKER CONTAINER EMPHASIZES MINIMAL IMAGES SIZE/CONSTRUCTION
3. FROM OPS PERSPECTIVE, CONTAINER IMAGE IS BLACK BOX
4. WRITE ONCE READ MANY
5. CONTAINERS ARE EPHEMERAL1

35. 1. MICROSERVICES – BUZZWORD OR SOMETHING DEEPER
2. 12-FORM FACTOR APPLICATION
3. APP CONTAINERS
4. CI/CD PIPELINE – REMOVE WASTE DON’T CUT THE COSTS
5. MANTL/SHIPPED – PIPELINE ON PREM
6. CI/CD IN AWS
7. FIN/ACK
AGENDA

36. CI/CD PIPELINE
– REMOVE WASTE DON’T CUT THE COSTS

37. LEAD TIME = CYCLE TIME + WAITING TIME
LEAD TIME = the time is takes to complete a process – from start to finish
CYCLE TIME = the time a product is being worked on
WAITING TIME = the time spent waiting around to be worked on

41. „Operations at web
scale is the ability
to consistently
create and deploy
reliable software
to an unreliable
platform that
scales horizontally”

42. Resilience, security,
scalability, availability
deployability, testability
are architectural concerns.

44. 1. MICROSERVICES – BUZZWORD OR SOMETHING DEEPER
2. 12-FORM FACTOR APPLICATION
3. APP CONTAINERS
4. CI/CD PIPELINE – REMOVE WASTE DON’T CUT THE COSTS
5. MANTL/SHIPPED – PIPELINE ON PREM
6. CI/CD IN AWS
7. FIN/ACK
AGENDA

45. MANTL/SHIPPED
– PIPELINE ON PREMISE

46. Why are you building infrastructure and not your application?

50. 1. Continuous Integration(CI)/Continuous Delivery(CD) platform
(build/deploy/run)
2. Application intent engine
3. Infrastructure monitoring
4. Contiv (Infra Policy Enforcement)
WHAT PROBLEMS
DOES SHIPPED SOLVE

51. BUILD STEP

53. DEPLOY STEP

54. DEPLOY STEP

55. APPLICATION INTENT

56. APPLICATION INTENT

57. 1. MICROSERVICES – BUZZWORD OR SOMETHING DEEPER
2. 12-FORM FACTOR APPLICATION
3. APP CONTAINERS
4. CI/CD PIPELINE – REMOVE WASTE DON’T CUT THE COSTS
5. MANTL/SHIPPED – PIPELINE ON PREM
6. CI/CD IN AWS
7. FIN/ACK
AGENDA

58. CI/CD

59. „DON’T REINVENT THE WHEEL,
JUST REALIGN IT”
― Anthony J. D’Angelo

60. HOW CAN HELP WITH PIPELINES?

62. 1. Do you bake the software, configuration and your code into the AMI
(à la Netflix)
2. Do you bake only the software and configuration, and download the code
on boot
3. Do you use a clean OS AMI, and do everything on boot
(à la chef server/puppet)
BAKING AMIs

63. AWS CODEPIPELINE

69. With custom actions, the job
worker drives the interaction
between AWS CodePipeline and
other applications or services

70. With AWS Lambda-based
actions, AWS CodePipeline
drives the integration with
Lambda, which then connects
with other applications
or services

82. BLUE / GREEN APPROACH

84. CLASSIC DNS CUTOVER
/ CANARY APPROACH

85. Start with current
app environment
Deploy a new
app environment

86. Test green stack
Gradually
cut traffic over
via DNS

87. Monitor your
environmets
If needed roll
back to blue one

88. SWAP ECS SERVICE WITH ELB

90. CREATE GREEN
SERVICE
WITH NEW
TASK DEFINITION
AND MAP
TO EXISTING ELB

91. SCALE UP
GREEN
SERVICE BY
INCREMENTING
NUMBER
OF TASKS

95. YOUR TEAM CARES ABOUT DOWNSTREAM TEAMS

97. Dziękuję
KAROL JUNDE
Network Solutions Architect
+48 661 690 027
karol.junde@trecom.pl