GraphQL Fastify vs Apollo Server — Learnings from the real world

1

Redis

Since we were focusing to deliver the MVP, we didn’t concern about using a good cache database like Redis, but we’ve prepared our server to be ready for it, however, we stayed with the in-memory cache. The integration with a Redis cache was our new attempt to mitigate the persisting problem. This improvement would decrease the number of read/write operations in the memory and remove the redundancy of data between pods, these were the main topics why we suspected that the problem was with the in-memory cache.

#Key-Value Database #NoSQL Databases #Databases 183 social mentions

2

Kubernetes

Once the Minimum Viable Product (MVP) was reached, we deployed the first version to production on a Kubernetes service. After a while, we started to have some traffic on our server, as expected, and the problems were also appearing.

#Developer Tools #DevOps Tools #Containers As A Service 280 social mentions

3

Hey Load Generator

To compare the two servers, we used two packages. The first one was ClinicJS, an open-source set of tools used to diagnose NodeJS performance issues, which also gives you suggestions and points you in a direction to fix the diagnosed problems. The second one was hey, a CLI tool to send some load to the server. Below we show how we use them and the results of these comparisons.

#Load Generator #Developer Tools #DevOps Tools 25 social mentions

4

ExpressJS

In this article, we’ll be discussing a problem that we faced when using Apollo GraphQL in a production environment and how we managed to solve it. To do so, we’ll compare two different GraphQL runtime solutions, one using ExpressJS and the other one using Fastify, and also analyze the implementation details and show you some benchmarks.

#JavaScript Framework #Node.js Framework #Web Frameworks 424 social mentions

5

Chrome DevTools

Then we started to debug using the chrome devtools to take heap snapshots while we were running some load tests and we couldn’t find any memory leak in our code.

#Automated Testing #Software Development #Testing 37 social mentions