Tuesday, July 07, 2015
Ryan Stevens, Lending Club
Engineers are told throughout their career not to reinvent the wheel. Frameworks allow engineers to concentrate on domain-specific logic and bypass wasted time writing tedious, boilerplate code. Have you ever wondered why there are so many frameworks to choose from? They differ in their design choices, in which patterns developers are forced to adhere, how fervently dogmatic their followers are, etc. Then a new one comes along and people justify yet another framework rewrite in the name of superior technology.
This talk will journey into the sometimes taboo subject of creating your own framework. This may seem counter-intuitive when it seems like we should be converging to the “ultimate” framework as an industry. Yet under the right circumstances, embracing a home-grown framework can have its merits and is worth exploring. Key takeaways:
Yunong Xiao, Netflix
Building services in Node.js is easy. Running and supporting them at scale in production is hard. At Netflix, we embarked on a journey to use Node and its ecosystem of modules as the foundation to build a new website for tens of millions of our subscribers.
In this talk, I will share our experiences building and scaling our Node stack — the foundation of our web UI. Along the way, find out about the methodology, tools and modules we used. Peer behind the curtain as I tell the story about how we optimized CPU utilization, fixed memory leaks, and increased visibility. You'll learn how and why we built our Node stack to be both observable and resilient — attributes which help us avoid and quickly mitigate issues in production.
Yunong is a senior Node.js software engineer at Netflix, where he's architecting NetflixUI's transition to Node. Previously he worked on distributed systems, cloud computing, and big data at AWS and Joyent — where he launched AWS IAM and the Joyent Manta Object Store and Computer Service. He is also the maintainer of restify, a popular Node.js REST framework.
Sameera Rao, Paypal