Scaling Your Node.JS API Like a Boss (Part Two)

While doing that, I will outline how to choose the container architecture for your (virtual) machines, how you can roll out updates to service without disrupting the users, and how you fail gracefully when things on a node go haywire.

I will also also cover tracking down memory leaks and coming up with short-term (i.e., restarting your nodes when they become too beefy) and long-term (i.e., actually spotting where the leaks are and fixing them) solutions to address them.

When you dive deeper and deeper into the rabbit hole, you soon realize that scalability is a tough job that requires careful planning and consideration. The bottom line is that designing any system to scale is a never-ending adventure, and there is no limit on how deep you can dive.

[tofuman]

If anyone watching this video considered themselves to be decent Backend developers, their ego probably regresses to zero by the end of this video.

[redraushan]

Stunned by the amount of knowledge you possess.

[jonmathew]

A beginner here. Would you suggest starting with node when I know task is compute intensive? (Was planning to use Django restful) Also can you suggest some resources for advanced topic like this. Thanks in advance.

[ShasakRaina]

Any mini project that one can do to employ these techniques, on their own system not requiring multiple machines or paid VMs?

[arunpriyadarshi]

Where can i find this ppt and associated links ?