Download as PDF, PPTX
![MONOLITHIC APPLICATION VS MICROSERVICES
EX’ - LETS ADD FOLLOW BUTTON TO A RESTAURANT PAGE
▸ Monolithic App
▸ Create new dir
▸ Adding bunch of code
▸ Add the routes
▸ 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/44229349-c488-4a66-a5d4-fdcd96686064-160204024823/85/microservice-15-320.jpg)
![DEMO - COUNTER
[POST] /counter
Client
Client
Server
Increment
Server
Decrement
Redis
In this example the communication is sync I would recommend using async
[GET] /counter](https://image.slidesharecdn.com/44229349-c488-4a66-a5d4-fdcd96686064-160204024823/85/microservice-21-320.jpg)
Uploaded byDoron Segal
microservice
This document discusses the evolution of web application development from monolithic applications to microservices architectures. It provides examples of how adding a new "follow" button functionality would differ between a monolithic app versus separate services. It then demonstrates a simple counter app implemented with Docker, Node.js, and Redis to illustrate the benefits of microservices like fault isolation, scalability, and easier debugging. The key advantages of microservices are discussed as isolation, immutability, and having each service focus on a specific problem.
microservice
- 1. DOCKER, NODE.JS, REDIS MICROEVERYTHING T @SEGALDORON G DORON2402/DOCKER-NODEJS-REDIS
- 2. A LITTLE BITOF HISTORY…
- 3. YOU NEED… PHP 3,MYSQL, IPTABLES, ETC.. 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 ▸ Create new dir ▸ Adding bunch of code ▸ Add the routes ▸ 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. DEMO - COUNTER [POST]/counter Client Client Server Increment Server Decrement Redis In this example the communication is sync I would recommend using async [GET] /counter
- 22. THANK YOU! THE KEYSARE - ISOLATION - IMMUTABILITY
- 23. 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!