Recomendados
Más contenido relacionado
Destacado
Node event loop
- 2. Wants to see if his team member Pam should get a raiseAlan Wants to schedule a 2 week vacation Bob
- 3. ● Check Pam’s sales figures ● Compare to company performance ● Give her the raiseAlan ● Check available vacation hours ● Schedule his vacation Bob
- 4. IIS Alan Bob (Empty) Jim Come into my office
- 5. IIS Alan Bob (Empty) Jim I need Pam’s sales figures
- 6. IIS Alan Bob (Empty) Jim Jim logs into sales tracker and looks up info
- 7. IIS Alan Bob (Empty) Jim few min later gives answer
- 8. IIS Alan Bob (Empty) Jim How much vacation do I have left?
- 9. IIS Alan Bob (Empty) Jim Jim logs out of sales tracker and into vacay tracker
- 10. IIS Alan Bob (Empty) Jim few min later gives answer
- 11. IIS Alan Bob (Empty) Jim Few more rounds of Jim logging in/out. Alan and Bob wait it out
- 12. Alan Bob An hour later they’re back at their desks IIS oh no, their work has piled up! :(
- 13. Threads take up resources Threads cause context switching Synchronous operations must wait to continue working IIS
- 14. Node Intern 1 Jim Intern 2 Door slot
- 15. Node Intern 1 Jim Intern 2 Sales query from Alan
- 17. Node Intern 1 Jim Intern 2 Vacay query from Bob
- 20. Node Jim calls Alan with the answer for his query Meanwhile, Alan has been productive with his work
- 21. Single thread saves RAM and CPU Queue for incoming I/O requests Asynchronous ops, your code can keep working while you wait for a callback Node