Download to read offline
![MONOLITHIC APPLICATION VS MICROSERVICES
EX’ - LETS ADD FOLLOW BUTTON TO A RESTAURANT PAGE
▸ Monolithic App
▸ adding bunch of code
to existing code.
▸ new directory
▸ bunch of new file
▸ Micro Service
▸ Creating new service
▸ Routing traffic to our service
▸ [POST] /users/:id/follow/:id
▸ [DELETE] /users/:id/follow/:id
▸ [GET] /users/:id/follow/:id](https://image.slidesharecdn.com/microservice-160201062407/85/Microservice-15-320.jpg)
Uploaded byDoron Segal
Microservice
This document discusses the evolution of web application architectures from monolithic PHP/MySQL applications in the early 2000s to modern microservice architectures using containers and technologies like Docker. It outlines some of the key benefits of microservices like independent deployment of services, improved scalability and debugging. The document demonstrates these concepts through an example of adding a "follow" feature to a restaurant page, showing how it can be more easily implemented and debugged as a separate microservice rather than within a monolithic application.
Microservice
- 1. DOCKER, NODE.JS, REDIS MICROEVERYTHING T @SEGALDORON G GITHUB.COM/DORON2402/OT-MICROSERVICE-TALK
- 2. A LITTLE BITOF HISTORY…
- 3. YOU NEED YOUR PHP3 WITH MYSQL And your web server is ready! EARLY 2000
- 4.
- 5.
- 6.
- 7.
- 8. DOCKER HOW DOCKER CHANGETHE WORLD ▸ Deployment ▸ Scaling ▸ Thinking in microsite ▸ Debugging ▸ Shipping ▸ Discovering
- 9.
- 10.
- 11.
- 12. THE OLD WAY MONOLITHICAPPLICATION ▸ Lots of engineers work on the same code base ▸ Scary deployment (all eggs in one basket) ▸ One thing doing too many things ▸ Hard to debug ▸ Scaling?!
- 13. WELCOME TO THEFUTURE MICRO SERVICE ARCHITECTURE ▸ Smaller code base ▸ Smaller team ▸ Fast & Small deployment ▸ Each service solve a specific problem ▸ Stateless ▸ Product VS Services ▸ Async Services
- 14. MONOLITHIC APPLICATION VSMICROSERVICES EX’ - LETS ADD FOLLOW BUTTON TO A RESTAURANT PAGE
- 15. MONOLITHIC APPLICATION VSMICROSERVICES EX’ - LETS ADD FOLLOW BUTTON TO A RESTAURANT PAGE ▸ Monolithic App ▸ adding bunch of code to existing code. ▸ new directory ▸ bunch of new file ▸ Micro Service ▸ Creating new service ▸ Routing traffic to our service ▸ [POST] /users/:id/follow/:id ▸ [DELETE] /users/:id/follow/:id ▸ [GET] /users/:id/follow/:id
- 16. MONOLITHIC APPLICATION VSMICROSERVICES OH NO WE HAVE A BUG?!?
- 17. MONOLITHIC APPLICATION LETS TRYTO FIND THE BUG?!? ▸ Most importantly our site is DOWN!!
- 18. MICROSERVICES OUR SITE ISSTILL UP ▸ Worse case scenario our `follow` button is missing or not saving the state after refresh
- 19. DEMO NOW THAT WEUNDERSTAND WHY MICRO SERVICE IS THE WAY TO GO LETS DEMO
- 20.
- 21. THANK YOU! THE KEYIS ISOLATION QUESTIONS?
- 22. THANK YOU! IF YOUCAN’T THINK ABOUT ANY QUESTION PING ME LATER ON TWITTER @SEGALDORON YOU CAN ALSO FIND THE CODE HERE: HTTPS://GITHUB.COM/DORON2402/DOCKER-NODEJS-REDIS SLIDESHOW AND LINKS WILL BE POST ON THE MEETUP PAGE THANK YOU!