An efficient server implies a lower cost of the infrastructure, a better responsiveness under load and happy users. How can you efficiently handle the resources of your server, knowing that you are serving the highest number of requests as possible, without sacrificing security validations and handy development?
Enter Fastify. Fastify is a web framework highly focused on providing the best developer experience with the least overhead and a powerful plugin architecture. It is inspired by Hapi and Express and as far as we know, it is one of the fastest web frameworks in town.
Install with npm:
npm i fastify --save
Install with yarn:
yarn add fastify
// Require the framework and instantiate it
const fastify = require('fastify')({
logger: true
})
// Declare a route
fastify.get('/', (request, reply) => {
reply.send({ hello: 'world' })
})
// Run the server!
fastify.listen(3000, (err, address) => {
if (err) throw err
fastify.log.info(`server listening on ${address}`)
})with async-await:
const fastify = require('fastify')({
logger: true
})
fastify.get('/', async (request, reply) => {
reply.type('application/json').code(200)
return { hello: 'world' }
})
fastify.listen(3000, (err, address) => {
if (err) throw err
fastify.log.info(`server listening on ${address}`)
})Do you want to know more? Head to the Getting Started.
Good tools make API development quicker and easier to maintain than doing everything manually.
The Fastify CLI is a command line interface tool that can create new projects, manage plugins, and perform a variety of development tasks testing and running the application.
The goal in this guide is to build and run a simple Fastify project, using the Fastify CLI, while adhering to the Style Guide recommendations that benefit every Fastify project.
Open a terminal window.
npm install fastify-cli --global
Generate a new project and default app by running the following command:
fastify generate
For more information, see the Fastify CLI documentation.
.listen binds to the local host, localhost, interface by default (127.0.0.1 or ::1, depending on the operating system configuration).
See the documentation for more information.
- Highly performant: as far as we know, Fastify is one of the fastest web frameworks in town, depending on the code complexity we can serve up to 30 thousand requests per second.
- Extendible: Fastify is fully extensible via its hooks, plugins and decorators.
- Schema based: even if it is not mandatory we recommend to use JSON Schema to validate your routes and serialize your outputs, internally Fastify compiles the schema in a highly performant function.
- Logging: logs are extremely important but are costly; we chose the best logger to almost remove this cost, Pino!
- Developer friendly: the framework is built to be very expressive and help the developer in their daily use, without sacrificing performance and security.
Machine: Intel Xeon E5-2686 v4 @ 2.30GHz (4 cores, 8 threads), 16GiB RAM (Amazon EC2 m4.xlarge)
Method:: autocannon -c 100 -d 40 -p 10 localhost:3000 * 2, taking the second average
| Framework | Version | Router? | Requests/sec |
|---|---|---|---|
| hapi | 17.5.1 | ✓ | 22,139 |
| Express | 4.16.3 | ✓ | 22,265 |
| Restify | 7.1.0 | ✓ | 23,604 |
| Koa | 2.5.1 | ✗ | 25,378 |
| Fastify | 1.6.0 | ✓ | 37,433 |
| - | |||
http.Server |
8.11.2 | ✗ | 29,855* |
Benchmarks taken using https://github.com/fastify/benchmarks. This is a synthetic, "hello world" benchmark that aims to evaluate the framework overhead. The overhead that each framework has on your application depends on your application, you should always benchmark if performance matters to you.
* Node.js core is slower than Fastify because of nodejs/node#20798. The problem has already been solved in Node.js 10.
Getting StartedServerRoutesLoggingMiddlewaresHooksDecoratorsValidation and SerializationLifecycleReplyRequestError HandlingContent Type ParserPluginsTestingBenchmarkingHow to write a good pluginPlugins GuideHTTP2Long Term SupportTypeScript and types support
中文文档地址
Fastify is the result of the work of a great community. Team members are listed in alphabetical order.
- Matteo Collina, https://twitter.com/matteocollina, https://www.npmjs.com/~matteo.collina
- Tomas Della Vedova, https://twitter.com/delvedor, https://www.npmjs.com/~delvedor
- Tommaso Allevi, https://twitter.com/allevitommaso, https://www.npmjs.com/~allevo
- Dustin Deus, https://twitter.com/dustindeus, https://www.npmjs.com/~starptech
- Trivikram Kamat, https://twitter.com/trivikram, https://www.npmjs.com/~trivikr
- Luciano Mammino, https://twitter.com/loige, https://www.npmjs.com/~lmammino
- Cemre Mengu, https://twitter.com/cemremengu, https://www.npmjs.com/~cemremengu
- Evan Shortiss, https://twitter.com/evanshortiss, https://www.npmjs.com/~evanshortiss
- James Sumners, https://twitter.com/jsumners79, https://www.npmjs.com/~jsumners
- Nathan Woltman, https://twitter.com/NathanWoltman, https://www.npmjs.com/~nwoltman
Past Collaborators
This project is kindly sponsored by:
Past Sponsors:
Licensed under MIT.