Node.js Enterprise Middleware
14 likes4,624 views
This document discusses Node.js as an enterprise middleware platform. It provides context on soft real-time applications and cloud computing needs. Node.js uses an event-driven, non-blocking I/O model with callbacks to achieve high concurrency levels. Its use of JavaScript and modular package ecosystem allow for rapid development. Key benefits highlighted include performance, scalability, agility, and cost savings. Success stories from companies like PayPal, LinkedIn, and Yahoo adopting Node.js are also mentioned.
![[212] large scale backend service develpment](https://cdn.slidesharecdn.com/ss_thumbnails/221largescalebackendservicedevelpment-150915001346-lva1-app6892-thumbnail.jpg?width=560&fit=bounds)
Ad
More Related Content
What's hot (20)
Viewers also liked (20)
Ad
Similar to Node.js Enterprise Middleware (20)
Ad
Recently uploaded (20)
![Pixologic ZBrush Crack Plus Activation Key [Latest 2025] New Version](https://cdn.slidesharecdn.com/ss_thumbnails/fashionevolution2-250322112409-f76abaa7-250428124909-b51264ff-250504160528-fc2bb1c5-thumbnail.jpg?width=560&fit=bounds)
Node.js Enterprise Middleware
- 1. Node.js Enterprise Middleware Behrad Zari [email protected] June 2014 Tehran/Iran Chapter http://www.acm.org.ir
- 3. Context Soft Real-Time Push-Based Applications twitter, chat, sport bets, mobile, … SPA many req/sec with low response times, sharing things like validation code between the client and server, FAT client Cloud SaaS, PaaS, DBaaS
- 4. Context (cont.) Queued Inputs High concurrency, DB bottleneck, Brokers (MOM) JSON-based REST-full Interfaces Service mediation & federation (SOA) Polyglot-Database Applications NoSQL + Relational + Distributed Caches in a rapid agile development fashion
- 5. Motivation: grow Cloud Enterprise Service Farms IoT Mobile Rapid Change Data Volume Integration Performance + Scalability Concurrency
- 7. PHP (1994) a thread/request No Pooling
- 8. Java Servlet (1995) a thread/request with pooling in container = pre-allocation
- 9. Problem 1? Context switching is not free Execution stacks take up memory A quick calculation: assuming that each thread potentially has an accompanying 2 MB of memory with it, running on a system with 8 GB of RAM puts us at a theoretical maximum of 4000 concurrent connections, plus the cost of context- switching between threads. For massive concurrency, cannot use an OS thread for each connection
- 10. Problem 2? We always do I/O result = db.query("select somthing from T"); // use result which is blocking
- 11. I/O latency L1: 3 cycles L2: 14 cycles RAM: 250 cycles DISK: 41,000,000 cycles NETWORK: 240,000,000 cycles
- 12. Non-Blocking IO
- 13. Non-Blocking IO Callbacks + Polling Epoll, POSIX AIO, … Event-Driven While there are events to process e = get the next event perform the action requested by e in a thread if e’s thread is complete and e has an associated callback call the callback
- 14. Event Loop
- 15. Now… var result = null; db.query("select..", function (passedResult) { // use passed result… result = passedResult; }); console.log( result ); // what’s result now?
- 16. Concurrency Models Thread-based Locks and Shared State VS Event-driven Concurrency I/O parallelism without requiring CPU parallelism no synchronization is required maximize resource efficiency
- 17. Where were you!? Why everyone isn’t using event loops, callbacks, non-blocking IO? Cultural Infrastructural
- 18. Cultural This is How we’re taught I/O: puts("Enter your name: " var name = gets(); puts("Name: " + name);
- 19. Cultural (2) Rejected as too complicated puts("Enter your name: "); gets(function (name) { puts("Name: " + name); });
- 20. Missing Infrastructure Single threaded event loops require I/O to be non-blocking Most libraries are not.
- 21. Too Much Infrastructure EventMachine, Twisted, AnyEvent, Apache Mina, Java nio, … users are confused how to combine with other available libraries
- 22. Why Javascript? Javascript designed specifically to be used with an event loop purely: Anonymous functions, closures Only one callback at a time I/O through DOM event callbacks culture of Javascript is already geared towards evented programming
- 23. What is Node.js? Node.js emerged from a project at cloud service provider Joyent in 2009
- 24. Node.js Project on www.ohloh.net
- 25. Node.js Architecture Cross-platform asychronous I/O Open source JavaScript engine, Optimizer, JIT, inline caching, GC
- 27. Node.js Ecosystem Modules (CommonJS Securable Module) Think Modular, not Monolithic Fine grained pieces of logic
- 28. innovation through modularity npm module (package) manager, taking care of recursive dependencies and resolving collisions, … Publishing a node module fulfills satisfaction for developers much greater than contributing to a larger code base
- 30. Dependencies are your friends Do not force everyone to agree on the same version of a module lets you avoid dependency hell by modifying the require.paths at runtime
- 32. Node.js Ecosystem event loop and event handlers yields an IoC: why we needed IoC? how is real world?
- 33. Node.js TCP Server Socket
- 34. RPC (RMI) in node.js Dnode Server Dnode Client
- 35. How to scale our single-threaded high performance node.js service? with node.js built-in Cluster module
- 36. Cluster Module Node.js achieves scalability levels of over 1Million concurrent connections N-Copy, Shared Socket, Round-Robin
- 37. Node.js Scalability Model independently scale the subsystems a JavaEE 3-tier app is actually not written with Horizontal clustering in mind Horizontal, share-nothing
- 39. Decentralized Responsibility & Data Polyglot Persistence continuousdeployment Independently deployable services http://martinfowler.com/articles/microservices.html gracefully fail SPoF Easy monitoring
- 41. Node.js Middleware Benefits Performance & Scalability single threaded event loop + async IO (built-in) easy high performance middleware stack (as a primary goal) hard to write slow programs Agile and lightweight development Javascript modularity TDD, BDD, automated tests(mocha,…) avoid build step (live coding) Auto Restart and Continuous Deployment process monitoring (forever, pm2,…) fail fast: just fail & let some other process do error recovery
- 42. Node.js Business Benefits Motivation high risk fast prototyping continuous delivery Productivity an enterprise scale web server in 5 lines >80K modules on npm (growing ecosystem) Comet, Pervasive Computing, REST, MOM, Integration? Developer Joy more happy, works better, more developers join Cost Savings fewer developers smaller iterations + more velocity => half-time Less hardware
- 44. Success Stories Name Usage Paypal $3.5 billion IN 2011, In Java Spring: unfriendly environment for front- end engineers With Java, when deployed to a staging server was a few thousandths of a second wait in Node.js, Bill Scott , 33-50% fewer lines of code to get a job done PayPal has redone 22 of its customer applications: PayPal Funding Source, PayPal Account Details, PayPal LogOn, and Wallet eBay released ql.io, an event-driven aggregation tool for API consumption LinkedIn massive performance gains with Node Yahoo! Mojito, 200 developers, 500 private, 800 extra modules, 2,000,000 req/min Walmart mobile development, no server down time! Oracle Nashorn: a JVM-based JavaScript engine
- 47. Node.js Project on Ohloh (2014) 8000 lines of C/C++, 2000 lines of Javascript, 14 contributors @ 2009
- 48. .end() References • It was a huge list, please surf the web as me, or contact me :)
- 49. Let me know if you have… High Throughput & Scalable backend NoSQL, Data Engineering, BI Enterprise Integration problems.
- 50. Supplementary Content... – Js anti-pattern 1: Callback hell
- 51. JS Callback hell
- 52. Solution 1: async module