This document provides an overview of microservices and tools for developing microservices architectures. It discusses some of the benefits of moving from monolithic architectures to microservices, including improved scalability, fault isolation, and independent deployability. It then introduces Docker and Docker Compose as useful tools for building and testing microservices. A demo is shown of using Dockerfile to build an image and Docker Compose to define and run multiple services locally. The document concludes by discussing challenges of microservices and the need for tools like Kubernetes to manage complexity at scale.

1. MICROSERVICES, LA
RISPOSTA CHE (FORSE)
CERCAVI!
FIRENZE
22 MARZO 2018

2. !
I’M THOMAS
NICE TO MEET YOU!

3. MICHELE
FRANZIN
@REALFUZZY

4. AGENDA

5. INTEREST IN
#MICROSERVICES

7. DISCLAIMER
our personal experience
ideas, comment, etc… are welcome
subject is wide, so I’d love to hear your thoughts :-)
it’s not a code talk (some source showed)

8. THE
MONOLITH

9. THE (SOMETIMES EVIL) MONOLITH
http://www.infoq.com/articles/microservices-intro

10. easy to develop

11. IDEs & development
tools support

12. easy to test

13. simple to deploy

14. works well for
relatively small apps

15. AFTER A WHILE…
http://www.qcodemag.it/wp-content/uploads/2014/09/favela.jpg

16. growth overloads
everything

17. difficult to adopt new
technologies

18. often stuck with the
starting choices

19. doesn’t scale to
long-lived application

20. BUAHAHAHAHA!
I AM THE
MONOLITH!
COME TO THE
WORLD TO BRING
IMMOBILISM AND
COMPLEXITY!

21. MONOLITH

22. MONOLITH
ARCHITECTURE ARCHITECTURE
MICROSERVICEIC

23. ARCHITECTURE
is the keyword

24. WHY MICROSERVICES
• suite of small services
• running in its own process
• communicating with lightweight mechanisms
• built around business capabilities
• independently automated deployable
• technology agnostic

26. http://blog.arungupta.me/monolithic-microservices-refactoring-javaee-applications/

27. EXPECTATIONS
http://www.wallpaperawesome.com/wallpapers-awesome/

28. relatively small

29. easier to understand

30. easier to scale
development

31. improve fault isolation

32. develop & deploy
independently

33. no vendor lock

34. improves
tuning & scaling

35. - additional complexity of a distributed system
- tools/IDEs are monolithic applications oriented
- testing is more difficult
- must implement the inter-service communication
- increase memory consumption

37. 1ST WEEK

38. Divide et Impera

41. "

42. "

43. "

44. "

46. 2ND WEEK

47. IT WAS NOT SO GOOD

51. THE ONLY WAY TO MAKE
SOFTWARE SECURE,
RELIABLE, AND FAST IS
TO MAKE IT SMALL.
Andrew S. Tanenbaum

52. #

53. #

54. #

56. 6TH MONTH

58. 3 days * 2 people
=
6 workdays!
⬇
%

59. #

60. OUR MICROSERVICES TECHNOLOGY/TOOLS

62. &

63. & '

64. ? days * ? people
=
? days!

66. (

67. Simulates isolate systems(like production)
Usable in more OS
Ready to use
Easy to install and use
(

68. )

69. )

70. *

71. Simulates isolate systems(like production)
Usable in more OS
Ready to use
Easy to install and use
(

72. DOCKER FOR MAC/WINDOWS
Docker for Mac/Windows is an easy-to-install
desktop app for building, debugging and testing
Dockerized apps on a Mac/PC.
+

73. Docker platform
Docker compose
Docker CLI
Docker Notary CLI

74. Simulate isolate systems
Usable in more OS
Ready to use
Easy to install and use
,

75. Docker platform
Docker compose
Docker CLI
Docker Notary CLI

77. DEMO TIME
&

78. DEMO FILES
•Dockerfile
•docker-compose.yml

79. DOCKER IMAGE

80. DOCKER IMAGE

81. DOCKER IMAGE
FROM ruby
RUN apt-get update -qq && apt-get install -y build-essential
libpq-dev nodejs
RUN mkdir /my_app
WORKDIR /my_app
File: ./my_app/Dockerfile

82. DOCKER IMAGE
FROM ruby
RUN apt-get update -qq && apt-get install -y build-essential
libpq-dev nodejs
RUN mkdir /my_app
WORKDIR /my_app
File: ./my_app/Dockerfile

83. https://hub.docker.com/

84. DOCKER IMAGE
FROM ruby
RUN apt-get update -qq && apt-get install -y build-
essential libpq-dev nodejs
RUN mkdir /my_app
WORKDIR /my_app
File: ./my_app/Dockerfile

85. DOCKER IMAGE
FROM ruby
RUN apt-get update -qq && apt-get install -y build-essential
libpq-dev nodejs
RUN mkdir /my_app
WORKDIR /my_app
File: ./my_app/Dockerfile

86. CONTAINER AND MICROSERVICES: A ❤ STORY

87. DOCKER COMPOSE

88. version: '3'
services:
web:
build: ./my_local_app
command: bash -c "bundle install --path=/cache && rails s -p
3000 -b '0.0.0.0'"
ports:
- "4000:3000"
volumes:
- ./my_local_app/my_rails_app:/myapp
- ./my_local_app/gem_cache:/cache
depends_on:
- db
db:
image: postgres
DOCKER COMPOSE
File: ./docker-compose.yml

89. version: '3'
services:
web:
build: ./my_local_app
command: bash -c "bundle install --path=/cache && rails s -p
3000 -b '0.0.0.0'"
ports:
- "4000:3000"
volumes:
- ./my_local_app/my_rails_app:/my_app
- ./my_local_app/gem_cache:/cache
depends_on:
- db
db:
image: postgres
DOCKER COMPOSE
File: ./docker-compose.yml

90. version: '3'
services:
web:
build: ./my_local_app
command: bash -c "bundle install --path=/cache && rails s -p
3000 -b '0.0.0.0'"
ports:
- "4000:3000"
volumes:
- ./my_local_app/my_rails_app:/my_app
- ./my_local_app/gem_cache:/cache
depends_on:
- db
db:
image: postgres
DOCKER COMPOSE
File: ./docker-compose.yml

91. version: '3'
services:
web:
build: ./my_local_app
command: bash -c "bundle install --path=/cache && rails s -p
3000 -b '0.0.0.0'"
ports:
- "4000:3000"
volumes:
- ./my_local_app/my_rails_app:/my_app
- ./my_local_app/gem_cache:/cache
depends_on:
- db
db:
image: postgres
DOCKER COMPOSE
File: ./docker-compose.yml

92. version: '3'
services:
web:
build: ./my_local_app
command: bash -c "bundle install --path=/cache && rails s -p
3000 -b '0.0.0.0'"
ports:
- "4000:3000"
volumes:
- ./my_local_app/my_rails_app:/my_app
- ./my_local_app/gem_cache:/cache
depends_on:
- db
db:
image: postgres
DOCKER COMPOSE
File: ./docker-compose.yml

93. version: '3'
services:
web:
build: ./my_local_app
command: bash -c "bundle install --path=/cache && rails s
-p 3000 -b '0.0.0.0'"
ports:
- "4000:3000"
volumes:
- ./my_local_app/my_rails_app:/my_app
- ./my_local_app/gem_cache:/cache
depends_on:
- db
db:
image: postgres
DOCKER COMPOSE
File: ./docker-compose.yml

94. version: '3'
services:
web:
build: ./my_local_app
command: bash -c "bundle install --path=/cache && rails s -p
3000 -b '0.0.0.0'"
ports:
- "4000:3000"
volumes:
- ./my_local_app/my_rails_app:/my_app
- ./my_local_app/gem_cache:/cache
depends_on:
- db
db:
image: postgres
DOCKER COMPOSE
File: ./docker-compose.yml

95. version: '3'
services:
web:
build: ./my_local_app
command: bash -c "bundle install --path=/cache && rails s -p
3000 -b '0.0.0.0'"
ports:
- "4000:3000"
volumes:
- ./my_local_app/my_rails_app:/my_app
- ./my_local_app/gem_cache:/cache
depends_on:
- db
db:
image: postgres
DOCKER COMPOSE
File: ./docker-compose.yml

96. version: '3'
services:
web:
build: ./my_local_app
command: bash -c "bundle install --path=/cache && rails s -p
3000 -b '0.0.0.0'"
ports:
- "4000:3000"
volumes:
- ./my_local_app/my_rails_app:/my_app
- ./my_local_app/gem_cache:/cache
depends_on:
- db
db:
image: postgres
DOCKER COMPOSE
File: ./docker-compose.yml

97. WEB DB WEB DB
& '

98. 3 days * 2 people
=
6 workdays!

99. 0.25 days * 2 people
=
0.5 workday!
3 days * 2 people
=
6 workdays!

100. CONTAINER AND MICROSERVICES: A ❤ STORY

101. ▸ Microservices are cool, but be careful.
▸ Docker compose is very useful in develop env.
▸ How a portable and repeatable development
environment save your time, especially with
microservices architecture.
WHAT HAVE WE SEEN?

102. OK BUT…WHAT’S NEXT?
.

105. κυβερνήτης

106. κυβερνήτης
“helmsman of a ship”

107. CO-LOCATING HELPER PROCESSES
MOUNTING STORAGE SYSTEMS
DISTRIBUTING SECRETS
CHECKING APPLICATION HEALTH
REPLICATING APPLICATION INSTANCES
USING HORIZONTAL POD AUTOSCALING
NAMING AND DISCOVERING
BALANCING LOADS
ROLLING UPDATES
MONITORING RESOURCES
ACCESSING AND INGESTING LOGS
DEBUGGING APPLICATIONS
PROVIDING AUTHENTICATION AND AUTHORIZATION

108. HTTP://KOMPOSE.IO/
-> KOMPOSE ->

116. delivered is better than perfect

117. BUAHAHAHAHA!
I AM THE
MONOLITH!
COME TO THE
WORLD TO BRING
IMMOBILISM AND
COMPLEXITY!

118. ~385.7Mb
compressed

120. • single error in csv import should not abort the whole process
• realtime data input
• expose results to thousands of potential visitors (web)
• it should work on every browser (at least 5 years)
• expose functions to 3rd party applications via API
• sell to other companies as white-label SAAS (optional)
Changes!

121. how do you proceed?
should I take care of what?
any potential pitfalls?

123. <tag cloud>

125. Technical choices have
non-technical outcomes

127. – Melvin Conway, 1968
“organizations which design systems
… are constrained to produce
designs which are copies of the
communication structures of these
organizations”.

130. Non-technical choices
have technical outcomes

132. AWARENESS

136. / do practice
ask experts
0 be aware

137. HAPPY HACKING!

138. QUESTIONS ?
1 2

139. @realfuzzy
Michele Franzin
@rosse91
Thomas Rossetto
Thanks 4 coming!