Download to read offline
Uploaded byCommit University
Microservices, la risposta che (forse) cercavi!
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.
More Related Content
Similar to Microservices, la risposta che (forse) cercavi!
Microservices, la risposta che (forse) cercavi!
- 1. MICROSERVICES, LA RISPOSTA CHE(FORSE) CERCAVI! FIRENZE 22 MARZO 2018
- 2. ! I’M THOMAS NICE TOMEET YOU!
- 3.
- 4.
- 5.
- 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.
- 9. THE (SOMETIMES EVIL)MONOLITH http://www.infoq.com/articles/microservices-intro
- 10.
- 11. IDEs & development toolssupport
- 12.
- 13.
- 14. works well for relativelysmall apps
- 15.
- 16.
- 17. difficult to adoptnew technologies
- 18. often stuck withthe starting choices
- 19. doesn’t scale to long-livedapplication
- 20. BUAHAHAHAHA! I AM THE MONOLITH! COMETO THE WORLD TO BRING IMMOBILISM AND COMPLEXITY!
- 21.
- 22.
- 23.
- 24. WHY MICROSERVICES • suiteof small services • running in its own process • communicating with lightweight mechanisms • built around business capabilities • independently automated deployable • technology agnostic
- 26.
- 27.
- 28.
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 35. - additional complexityof a distributed system - tools/IDEs are monolithic applications oriented - testing is more difficult - must implement the inter-service communication - increase memory consumption
- 37.
- 38.
- 41.
- 42.
- 43.
- 44.
- 46.
- 47. IT WAS NOTSO GOOD
- 51. THE ONLY WAYTO MAKE SOFTWARE SECURE, RELIABLE, AND FAST IS TO MAKE IT SMALL. Andrew S. Tanenbaum
- 52.
- 53.
- 54.
- 56.
- 58. 3 days *2 people = 6 workdays! ⬇ %
- 59.
- 60.
- 62.
- 63.
- 64. ? days *? people = ? days!
- 66.
- 67. Simulates isolate systems(likeproduction) Usable in more OS Ready to use Easy to install and use (
- 68.
- 69.
- 70.
- 71. Simulates isolate systems(likeproduction) Usable in more OS Ready to use Easy to install and use (
- 72. DOCKER FOR MAC/WINDOWS Dockerfor 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 DockerCLI Docker Notary CLI
- 74. Simulate isolate systems Usablein more OS Ready to use Easy to install and use ,
- 75. Docker platform Docker compose DockerCLI Docker Notary CLI
- 77.
- 78.
- 79.
- 80.
- 81. DOCKER IMAGE FROM ruby RUNapt-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 RUNapt-get update -qq && apt-get install -y build-essential libpq-dev nodejs RUN mkdir /my_app WORKDIR /my_app File: ./my_app/Dockerfile
- 83.
- 84. DOCKER IMAGE FROM ruby RUNapt-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 RUNapt-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.
- 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 WEBDB & '
- 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 arecool, 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.
- 105.
- 106.
- 107. CO-LOCATING HELPER PROCESSES MOUNTINGSTORAGE 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.
- 116. delivered is betterthan perfect
- 117. BUAHAHAHAHA! I AM THE MONOLITH! COMETO THE WORLD TO BRING IMMOBILISM AND COMPLEXITY!
- 118.
- 120. • single errorin 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 youproceed? should I take care of what? any potential pitfalls?
- 123.
- 125.
- 127. – Melvin Conway,1968 “organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations”.
- 130.
- 132.
- 136. / do practice askexperts 0 be aware
- 137.
- 138.
- 139.