Node.js has had a transformational effect on the way we build software. However, convincing your organization to take a bet on Node.js can be difficult. My personal journey with Node.js has included convincing a few teams to take a bet on this technology, and this community. Let’s take a look at the case for Node.js we made at Google, and how you can make the case to bring it to your organization.
18. All I need to do is write some code
that creates an HTTP request with a very long timeout
and enable chunked transfer encoding. Then I’ll use another HTTP connection
to send data. Then I’ll just have to write some code in C# down at the HttpHandler level that manages
the state between these two connections, and then proxies the data over to an active VNC session living on another
machine. Oh and I guess I’ll have to handle all the connection resets, and provide a half decent API so other developers on the
team can actually use this thing.
Since coming out in 2009, Node.js has had a profound impact on my career. It’s shaped how I think about technology, and it’s changed the way I think about open source communities.
This is a bit of a different talk than the ones that I’m used to giving. I want to share my personal story with node.js - how we got started using it on my first team, and how it’s managed to become a key part of several companies where I’ve worked over the last few years.
