Leading microservices to the cloud with Nodejs

Microservice is a very vast topic. In this talk, I summarize why choosing Nodejs for building a microservice is a good choice, what are its benefits, its downsides and some code examples

Transcript

1. TWITTER/JPRIVILLASO GITHUB/JPRIVILLASO MEDIUM/@JPRIVILLASO LEADING MICROSERVICES TO THE CLOUD WITH NODEJS
2. RELEASE MANAGER
3. IT’S ALL ABOUT ARCHITECTURE
4. Microservice Microservice Microservice Microservice Microservice
5. A MICROSERVICE IS A SMALL APP WITH A VERY SPECIFIC PURPOSE IN THE CONTEXT OF AN ENTIRE APPLICATION, AND CAN BE ACCESSED FROM OTHER CONTAINERS OR MACHINES Me
6. REF. 1
7. CAN I USE ANY LANGUAGE FOR EACH MICROSERVICE? "YOU CAN USE ANY LANGUAGE FOR A MICROSERVICE IN THE SAME MANNER THAT YOU CAN RUN A MARATHON IN BOOTS” Joey Clover
8. A MICROSERVICE IS LANGUAGE AGNOSTIC A MICROSERVICE CAN INTERACT WITH ANYTHING A MICROSERVICE ROCKS. NODEJS ROCKS. Me
9. MICROSERVICES WITH NODEJS
10. MOTIVATION WHEN WE START THINKING ABOUT CLOUD SOLUTIONS, TONS OF PROBLEMS COME INTO PLAY. A MICROSERVICES’ ARCHITECTURE CAN SOLVE SOME OF THEM, BUT ALSO INTRODUCES NEW CHALLENGES TO YOUR APP.
11. BENEFITS OF USING NODEJS - EASY CODE - FAST CODE - SCALABLE CODE - GET RID OF A LOT PROBLEMS THAT ARE COMMON IN OTHER LANGUAGES
12. BUT… ISN’T NODEJS SINGLE THREAD ?
13. YES… BUT! NODE.JS IS PARTICULARLY WELL SUITED FOR APPLICATIONS THAT HAVE NUMEROUS CONCURRENT CONNECTIONS (UP TO ONE MILLION CONCURRENT CONNECTIONS)
14. HOW IS THAT? REF. 2 US CONF. Philip Roberts: https://www.youtube.com/watch?v=8aGhZQkoFbQ&vl=en
15. AND EACH REQUEST REQUIRES FEW CPU CYCLES. SO… SEEMS THAT WE’RE ON THE RIGHT WAY
16. DOWNSIDES? CPU INTENSIVE WORK CAN SLOW DOWN OR MAKE NODEJS COMPLETELY UNRESPONSIVE
17. THAT’S OK AND WE WILL FIND A WAY TO GET RID OF THOSE PROBLEMS
18. SO, WHAT WILL WE DO HERE AT ALL ?
19. TO PREVENT NODEJS TO BE UNRESPONSIVE, WE WILL SHOW HOW TO IMPLEMENT A MESSAGE-BASED SYSTEM
20. A COMMON ANALOGY IS THE POST OFFICE FIRST, A USER DELIVERS SOMETHING AT THE POST OFFICE
21. A COMMON ANALOGY IS THE POST OFFICE AFTER THAT, YOU LEAVE THE PLACE AND EXPECT THAT THE POST OFFICE WILL SEND A PERSON TO DELIVER YOUR PACKAGE
22. Producers Consumers Message Queue
23. Producers Consumers Message Queue
24. THIS IS WHAT WE CALL HORIZONTAL SCALING
26. SOME OF THE WORLD'S MOST SCALABLE ARCHITECTURES SUCH AS LINKEDIN AND NETFLIX ARE BASED ON EVENT-DRIVEN, ASYNCHRONOUS MESSAGING. Pivotal Blog
27. MOST COMMON USE CASES STREAMING PROCESSING LOGS TRANSACTIONS
28. LET’S CODE FOLKS! HTTPS://GITHUB.COM/JPRIVILLASO/ PUB_SUB_MICROSERVICES
29. REFERENCES 1. HTTPS://HACKERNOON.COM/MICROSERVICES-ARE-HARD-AN-INVALUABLE-GUIDE-TO-MICROSERVICES-2D06BD7BCF5D 2. HTTPS://STRONGLOOP.COM/STRONGBLOG/NODE-JS-IS-FASTER-THAN-JAVA/ 3. HTTPS://WWW.DEVBRIDGE.COM/ARTICLES/MESSAGING-WITH-RABBITMQ-IN-NODE-JS/ 4. BUILDING MICRO SERVICES BOOK, SAM NEWMAN
30. QUESTIONS?