Express VS fastify

Express.js Documentation

This guide walks through how to add GrowthBook feature flags to an Express.js application. It assumes you are starting from scratch, so if you already have an Express.js application, you can skip to step 2.

This guide is beneficial if you're using Express adapter. For NestJS applications utilizing the Fastify adapter, these links may be helpful:

First step: understanding what I'm working with. expressjs.com is the official documentation site for express, one of the most popular web frameworks for Node.js. While this was quick to grasp from their beautifully designed website, the journey was just beginning.

Link :https://www.npmjs.com/package/express

We'll start by initializing a Node project inside a chosen folder (nodejs-blog for me) with and installing a couple of dependencies that I feel like will make our lives easier, like Express, EJS, Marked, the good ol' body-parser and gray-matter.

Express Documentation

Express.js Official Website

I guess we could call it a major cleanup from v4 to v5? /me-thinks

https://github.com/fastify/fastify/blob/main/docs/Guides/Mig...

For example, Fastify removed the instanceof operatorfrom its codebase because it was causing problems for those developers that rely on jest as a testing framework.

Both are frameworks but NextJs is for Forntend (web app in browser that use ReactJs under the hood) and NestJs is for Backend (server app running on a server witch use Express or Fastify). The only thing similar between them is the typed language in which they were written.

Restify & Fastify Hapi

Let's create a sample Node API project we can work with throughout to build a new docker image. We will leverage Fastify to create an API that we configure via the fastify-cli.

Fastify

In setting out to build this service, we wanted to use gRPC for its APIs. We’ve been reaching for REST when building APIs so far, primarily out of necessity, i.e., our public APIs needed auto-generated client SDKs and docs for developers working with them. We built those APIs with Fastify and Typebox but felt burned by a code-first approach to generating an OpenAPI spec. I’ll spare you the details and save that experience/learning for another article. Suffice it to say we love gRPC’s schema-first approach. This blog post summarizes our feelings well