Our great sponsors
-
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
webpack
A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
-
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
-
-
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
TypeScript: While not a Node.js feature, the growth of TypeScript as a strongly-typed superset of JavaScript synergized with Node.js, offering static typing and future JS features.
PHP: While PHP had a rich ecosystem and a long history, it traditionally uses a multi-threaded, blocking model. Each incoming connection usually spawns a new thread, consuming more memory.
Django: Django, with its "batteries-included" philosophy, provided a comprehensive suite for web development. Yet, it was primarily synchronous in nature, relying on worker processes or threads.
Growth in Tooling: Tools like Babel allowed developers to use the latest JavaScript features without waiting for Node.js support, while Webpack streamlined bundling and module loading.
While the idea of server-side JavaScript was not novel, what powered Node.js was! The V8 engine, birthed by Google for Chrome, was now driving Node.js, bringing unparalleled speed and performance to JavaScript execution.
Sails.js: Sails.js pitched itself as the MVC framework for Node.js, bringing a Rails-like experience while being database agnostic.
Ruby on Rails: RoR is an elegant, convention-over-configuration framework. But, it too, generally followed a thread-based, blocking model.
If Node.js was the hero, then NPM (Node Package Manager) was its trusty sidekick. Born out of a need for sharing and reusing code, NPM did to Node.js what RubyGems did for Ruby. It was more than just a package manager; it was an enabler. With ease, developers could pull in a myriad of libraries or 'packages' to augment their apps.
It provided a structured environment for collaboration, partnership, and feature prioritization. In 2019 it merged with the JS Foundation to become the even more powerful OpenJS Foundation.
The year was 2009. Amidst the din of established server-side titans like PHP, Ruby on Rails, and Django, a new warrior geared up for the arena. A humble fellow by the name of Ryan Dahl presented to the world: Node.js.
Koa.js: By the team behind Express, Koa.js utilized async/await for middleware, resulting in cleaner and more readable code.
The landscape of JavaScript transformed dramatically with the introduction of ES6 (ECMAScript 2015).
import { serve } from "https://deno.land/[email protected]/http/server.ts";
Growth in Tooling: Tools like Babel allowed developers to use the latest JavaScript features without waiting for Node.js support, while Webpack streamlined bundling and module loading.
Related posts
- NestJS tip: how to change HTTP server timeouts
- Building a Dynamic Job Board with Issues Github, Next.js, Tailwind CSS and MobX-State-Tree
- Full Stack Web Development Concept map
- Don't go all-in Clean Architecture: An alternative for NestJS applications
- Utilizando Testcontainers para Testes de Integração com NestJS e Prisma ORM