Redis VS pino

To make data retrieval efficient and minimize the need to request data from the API on every page load, I implemented a caching strategy using the ioredis package, which is a popular redis client for Node.js for interacting with a Redis database.

5. ioredis

These are the objects I pass to ioredis to create my Redis instances (one for sessions and one as the main one):

In order to try and mitigate the OOMs. I read the Background Jobs in Node.JS with Redis blog post and implemented Heroku Data For Redis with ioredis, BullMQ and Throng,

Redis.Redis and Redis.Cluster at the end of the rule actually refer to the ioredis constructors, so to set them up, we must use the ioredis constructors.

ioredis is a popular Node.js client, providing a robust support for Redis Cluster.

To connect to Redis from your application, you will need a library that can perform that for you (Otherwise you have to reinvent the wheel). While I've been using IORedis for a nodeJS application in this demo, if you have been using a different language, you will have to look for different connectors like Lettuce for Java or perhaps go-redis for Go.

The Redis client I'm going to use today is ioredis, because its API is intuitive, very robust and with good performance.

Just create your own wrapper service around one of the existing nodejs redis clients, I used the following client https://github.com/luin/ioredis

Learn more about logging in Fastify and how to customize the Pino logger.

The Fastify framework includes the Pino logger by default (a really great logger with lots of cool features that doesn't compromise on performance). The framework itself allows a lot of really cool stuff, like controlling the level of logs at runtime.

Fastify provides a built-in logging mechanism based on Pino that allows you to capture various events in your applications. Once enabled, Fastify logs all incoming requests to the server and errors that occur while processing said requests. It also provides a convenient way to log custom messages through the log() method on the Fastify instance or the request object.

1. pino

Vitest is for frontend. Jest is not good for backend (I don’t like it for frontend either), take a look at this issue.

Have a look at https://github.com/pinojs/pino

NodeJS -> Pino, Winston, Bunyan, Npmlog, e.t.c.

Use a configurable logger like pino

Using pino as a logger, for every request on the _server_ , a unique ID generated client side in the headers, so a log may be something like: