⚙️ Task 7.2 -
has been all the rage among many developers for the past couple of years, although its popularity has also managed to enrage some others, who have unleashed a barrage of negative blog posts to point out its perceived
shortcomings. Still, while new and untested, Node continues to win more converts.
- In 2011 LinkedIn joined the movement when it opted to rebuild its core mobile services in Node. The
professional networking site, which had been relying on Ruby on Rails, was looking for performance and scalability gains. With its pervasive use of non-blocking primitives and a single-threaded event loop, Node
work on corresponding functions over on the server side.
- Kiran Prasad, who joined LinkedIn as senior director of mobile engineering in 2011, led the company’s transition to Node. On the server side, LinkedIn’s mobile frontend is now built entirely in Node.
- Prasad admits Node isn’t the best tool for every job, but upon analyzing LinkedIn’s system, Prasad and his team determined that what was needed to improve efficiency was an event-driven system.
- Node also proved
attractive because it’s thin and light while allowing for the direct manipulation of data objects.
- Prasad was well prepared for his role in mobile services at LinkedIn, having already accumulated years of experience in mobile apps working on the WebOS platform at Palm and Handspring in addition to stints as an independent developer of mobile Web software (as CEO at Sliced Simple and CTO at Aliaron).
- He talks here about LinkedIn’s adoption of Node.js with Kelly Norton and Terry Coatta. Norton was one of the first software engineers to work on the Google Web Toolkit (GWT) before cofounding Homebase.io, which
develops next-generation marketing tools.
- Coatta is CTO at Marine Learning Systems, which has developed a learning management system targeted at the marine industry. He previously worked for AssociCom, Vitrium Systems, GPS Industries, and Silicon
Task is successfully completed !!