The Evolution of Deploying Node on Servers and Platforms

Rate this content
Bookmark

NodeJS is a server-side representation of Javascript that can work well as an application's backend and can be run on various servers and infrastructures. In this talk, we'll be going through the journey of how Nodejs has been deployed over the years via various infrastructures from PaaS to Containers.


You can check the slides for Shedrack's talk here. 

8 min
17 Feb, 2022

Video Summary and Transcription

Today's talk covers the evolution of deploying Node on servers and platforms, including physical servers, monolith servers, PaaS, containers, and serverless. Node deployment has become easier over the years thanks to the evolution of Node.js. Each deployment method has its pros and cons, with serverless offering lower costs and simpler backend code. However, it also has drawbacks like vendor locking and unsuitability for long-term tasks. Overall, Node.js deployment has evolved from on-premise to containers to serverless.

Available in Español

1. Evolution of Node Deployment

Short description:

Today's talk is about the evolution of deploying Node on servers and platforms. We'll cover deployment on a server in a garage, monolith servers, platform as a service, containers, serverless, and function as a service. Node deployment has become easier over the years thanks to the evolution of Node.js. Let's start with Node deployed on a physical server in a garage. It provides a dedicated server for your application, giving you full control and security. However, it can be expensive, stressful to manage, and harder to optimize.

Hi, friends, welcome to my talk. The title for today is the evolution of deploying Node on servers and platforms. My name is Shedrak Akintayo. I am a developer relations engineer at Platform Message. I also do technical writing and I like to build communities, which I've done with Facebook Devs, Open Source Community Africa and DevRel community Africa.

So the table of content for today is we're going to be talking about how Node is deployed over the years in various forms. So how it is deployed on a server in a garage and how Node has been deployed on monolith servers, how Node has been deployed on a platform as a service and how Node has been deployed on containers. Then we'll do a quick rundown of how Node has been deployed on serverless and cloud function or function as a service. So let's get into it.

So the first thing I would want to highlight is that deployment is not easy. Trust me, anybody that has spent time working as a DevOps engineer deploying Node.js over the years, it's not as easy as it is. But thankfully, as Node.js evolves, the deployment becomes even easier. So thanks to the evolution of Node.js.

So the first thing we'll be talking about is Node deployed on a physical server in a garage. So basically building your own server. So before everything else, Node used to be deployed on a server in a garage actually. So the pros of it basically is that you have a dedicated Node server for just your application. So you have a lot of bare metal for your application. You can clone through your Node environment. To an extent it is secured because you handle everything that has to come with security which is a really good thing because you do not have to depend on any service provider. Whenever a provider is down, you don't have to worry about it. So this is how it was deployed basically. Node can be deployed on a physical server in a garage.

Next up is the cons. So it gets too expensive to set up. You know the manpower, the technical expensive to set up. Another one is it gets very stressful to manage because you are doing all the work yourself. The engineers are having to do all the work themselves. So this is another issue. And it's harder to optimise because most of the work is being done by you and your team, most of the part.

2. Deployment Methods

Short description:

Handling the optimization by yourself for deploying Node on a bare metal can be very tasking. Deploying Node.js on a monolith server allows for centralized deployment, but it becomes difficult to update as the application grows. NodeJS on a PaaS provides faster deployment and the ability to add additional data services, but it can be expensive at scale. Deploying Node on a container is the most popular method, making the app lightweight and resource efficient, but it can still be expensive and has vendor locking issues. Serverless deployment eliminates the need to worry about servers.

So handling the optimisation by yourself gets very, very tasking. So the requirements then, at the time where to be deployed on a bare metal, even though it's still being deployed like that now, not just as much as it was before. You need the early versions of Node. You need a lot of GPUs, you need RAMs, you need CPUs, basically, to deploy Node on, to be the Cisca server for yourselves, to deploy Node on it.

So the next stop is deploying Node.js on a monolith server. So basically, a monolith server consists of all parts of an application deployed on a single server, from the back end to the static part of the application. The pros of this particular way of deploying Node over the years is that the entire path is in a centralized server, and it's always a great choice to deploy Node as a monolith, so you can have all your applications in a single server, which is really, really great, because you can see every single thing you need to see, you can see all your applications coupled together. The cons is, as the application gets larger, it becomes difficult to update, and the memory requirements increase over time. For the requirements, you need a hosting server and NodeJS 12 upwards.

The next stop is NodeJS being deployed on a PaaS. So PaaS, Platform as a Service, also known as PaaS, involves, it provides a broad set of cloud-based application infrastructure and middleware resources via the cloud. An example of PaaS that you might have come across is Platform SH. Platform SH is quite different, because you can deploy a PaaS on containers, then Heroku, Vercel, Netlify, et cetera. The pro is NodeJS can be deployed faster, then you can also easily add additional data services to your Node application, then the cons is it can be very, very expensive at scale, and vendor locking also is another issue. The requirements to deploy Node on a PaaS are dependent on what the PaaS provider specifies generally.

Next up is deploying Node on a container. Now this is currently the most used way for deploying Node generally. A container is basically a lightweight piece of software that provides a run-time environment for your application. So platform.sh uses PaaS, but you get to deploy on container. It's basically a PaaS that you can use to deploy it on containers in Kubernetes, and also Docker. The pros, it makes your Node app lightweight and resource efficient. It's easy to manage and control your Node infrastructure. Adding external data services with your Node app is easier. Now the cons, it can be very expensive as still, and you also have issues with vendor locking. Whenever a vendor has issues, then it becomes a problem. Requirements to deploy Node on a PaaS are dependent on the container provider. That's the PaaS, the container provider, whoever is providing the container services. You also get to control what Node version memory disk size of your application.

Now, serverless is what we are basically going to talk about next. Serverless basically involves deploying your application without worrying about servers.

3. Serverless Deployment and Conclusion

Short description:

Servers are still present on a PaaS basis. Functions as a service allow modular code execution on the edge. Serverless has the advantages of lower costs, faster development, and simpler backend code. However, it also has cons such as vendor locking and unsuitability for long-term tasks. Overall, Node.js deployment has evolved from on-premise to containers to serverless.

Servers are still present, but it's on a PaaS basis. It also uses functions as a service, which is a serverless way to execute modular pieces of code on the edge. Example is which we've basically seen is AWS Lambda, which is one of the most important providers of serverless, and serverless.com.

Another pro, a pro of serverless, is lower costs. You get to build faster. Go to market becomes very, very faster. The backend code is simple because it's mostly in chunks as modular. It basically uses modular programming, which functions, so every part of your backend becomes a function.

Another part is, the cons of serverless, basically, is vendor locking, which is one of the major problems of serverless, and it's unsuitable for long-term tasks. In terms of scaling for a very, very long-term task, serverless doesn't really do well because it becomes a problem, basically, and it becomes very expensive, even though they sell it as something that provides lower cost.

So that's basically the end of my talk. I hope you've basically been able to know how Node.js have been deployed over the years, from point A to point B, from on-premise to containers, from monoliths to serverless. So my name is Chedrak Akintayo. I am a Developer Relations Engineer at Platform Message.

Check out more articles and videos

We constantly think of articles and videos that might spark Git people interest / skill us up or help building a stellar career

Node Congress 2022Node Congress 2022
26 min
It's a Jungle Out There: What's Really Going on Inside Your Node_Modules Folder
Top Content
Do you know what’s really going on in your node_modules folder? Software supply chain attacks have exploded over the past 12 months and they’re only accelerating in 2022 and beyond. We’ll dive into examples of recent supply chain attacks and what concrete steps you can take to protect your team from this emerging threat.
You can check the slides for Feross' talk here.
React Advanced Conference 2021React Advanced Conference 2021
19 min
Automating All the Code & Testing Things with GitHub Actions
Top Content
Code tasks like linting and testing are critical pieces of a developer’s workflow that help keep us sane like preventing syntax or style issues and hardening our core business logic. We’ll talk about how we can use GitHub Actions to automate these tasks and help keep our projects running smoothly.
DevOps.js Conf 2022DevOps.js Conf 2022
33 min
Fine-tuning DevOps for People over Perfection
Demand for DevOps has increased in recent years as more organizations adopt cloud native technologies. Complexity has also increased and a "zero to hero" mentality leaves many people chasing perfection and FOMO. This session focusses instead on why maybe we shouldn't adopt a technology practice and how sometimes teams can achieve the same results prioritizing people over ops automation & controls. Let's look at amounts of and fine-tuning everything as code, pull requests, DevSecOps, Monitoring and more to prioritize developer well-being over optimization perfection. It can be a valid decision to deploy less and sleep better. And finally we'll examine how manual practice and discipline can be the key to superb products and experiences.
Node Congress 2022Node Congress 2022
34 min
Out of the Box Node.js Diagnostics
In the early years of Node.js, diagnostics and debugging were considerable pain points. Modern versions of Node have improved considerably in these areas. Features like async stack traces, heap snapshots, and CPU profiling no longer require third party modules or modifications to application source code. This talk explores the various diagnostic features that have recently been built into Node.
You can check the slides for Colin's talk here. 

Workshops on related topic

Node Congress 2023Node Congress 2023
109 min
Node.js Masterclass
Workshop
Have you ever struggled with designing and structuring your Node.js applications? Building applications that are well organised, testable and extendable is not always easy. It can often turn out to be a lot more complicated than you expect it to be. In this live event Matteo will show you how he builds Node.js applications from scratch. You’ll learn how he approaches application design, and the philosophies that he applies to create modular, maintainable and effective applications.

Level: intermediate
Node Congress 2023Node Congress 2023
63 min
0 to Auth in an Hour Using NodeJS SDK
WorkshopFree
Passwordless authentication may seem complex, but it is simple to add it to any app using the right tool.
We will enhance a full-stack JS application (Node.JS backend + React frontend) to authenticate users with OAuth (social login) and One Time Passwords (email), including:- User authentication - Managing user interactions, returning session / refresh JWTs- Session management and validation - Storing the session for subsequent client requests, validating / refreshing sessions
At the end of the workshop, we will also touch on another approach to code authentication using frontend Descope Flows (drag-and-drop workflows), while keeping only session validation in the backend. With this, we will also show how easy it is to enable biometrics and other passwordless authentication methods.
Table of contents- A quick intro to core authentication concepts- Coding- Why passwordless matters
Prerequisites- IDE for your choice- Node 18 or higher
JSNation 2023JSNation 2023
104 min
Build and Deploy a Backend With Fastify & Platformatic
WorkshopFree
Platformatic allows you to rapidly develop GraphQL and REST APIs with minimal effort. The best part is that it also allows you to unleash the full potential of Node.js and Fastify whenever you need to. You can fully customise a Platformatic application by writing your own additional features and plugins. In the workshop, we’ll cover both our Open Source modules and our Cloud offering:- Platformatic OSS (open-source software) — Tools and libraries for rapidly building robust applications with Node.js (https://oss.platformatic.dev/).- Platformatic Cloud (currently in beta) — Our hosting platform that includes features such as preview apps, built-in metrics and integration with your Git flow (https://platformatic.dev/). 
In this workshop you'll learn how to develop APIs with Fastify and deploy them to the Platformatic Cloud.
JSNation Live 2021JSNation Live 2021
156 min
Building a Hyper Fast Web Server with Deno
WorkshopFree
Deno 1.9 introduced a new web server API that takes advantage of Hyper, a fast and correct HTTP implementation for Rust. Using this API instead of the std/http implementation increases performance and provides support for HTTP2. In this workshop, learn how to create a web server utilizing Hyper under the hood and boost the performance for your web apps.
React Summit 2022React Summit 2022
164 min
GraphQL - From Zero to Hero in 3 hours
Workshop
How to build a fullstack GraphQL application (Postgres + NestJs + React) in the shortest time possible.
All beginnings are hard. Even harder than choosing the technology is often developing a suitable architecture. Especially when it comes to GraphQL.
In this workshop, you will get a variety of best practices that you would normally have to work through over a number of projects - all in just three hours.
If you've always wanted to participate in a hackathon to get something up and running in the shortest amount of time - then take an active part in this workshop, and participate in the thought processes of the trainer.