redis-om-node VS apollo-server

How about using Redis OM https://github.com/redis/redis-om-node

In the code above, you could see some SQL-like query structure which makes the entire thing very friendly, this is made possible by Redis-om which is a new Redis client from Redis

Redis-OM Node Github Repo

Welcome to Ephemeral Chats, a TypeScript NodeJS app made with NestJS, Apollo GraphQL, RedisOM and MikroORM.

This sample shows how to define a Lambda function which uses Redis-om via AWS Cloud Development Kit. This is a fork of prisma-lambda-cdk sample repo which replaces mysql/postgres with redis stack & prisma with Redis-om.

Fast integration thanks to redis-om-node library. In dozen minutes, we are ready to start manipulating with documents.

The next step will be to create the entity and schema of our api (to be simpler I put it in the same file as the database configuration):

For the database, our app used Redis Database as the primary database for storage of information of users and quizzes. In order to interact with the redis database, we utilized Redis-OM, a Node JS library for redis that enables storage of JSON objects in Redis database. It also gives access to native redis-cli commands such as saving cache in redis directly which was pretty handy when storing questions in Redis cache whenever a student is taking a quiz and marking correct responses from a student.

Redis OM

Redis Om for Node - Object mapping, and more, for Redis and Node.js. Written in TypeScript. https://github.com/redis/redis-om-node

Another interesting point is that executing fetches on the server can allow developers to more easily leverage caching. Next.js already handles caching out-of-the-box and I’m curious to see if the wider adoption of RSC reduces the need to combine React with solutions like Apollo Server and Apollo Client. While there are other benefits to these tools, RSC could provide similar caching behavior without the need to invest in a GraphQL solution.

There are several GraphQL server implementations, however, for this tutorial, we'll utilize Apollo GraphQL's Apollo Server, a lightweight and flexible JavaScript server that makes it easy to build GraphQL APIs.

As I mentioned, their main GraphQL server package is[1], so that's where the confusion came from. Thanks.

[1] https://github.com/apollographql/apollo-server/blob/9817bc47...

While working on this blog post, I learned that Apollo Server, the most popular GraphQL server for typescript, uses a similar method for adding error codes to GraphQL. It even lets you add custom errors. Hopefully, someday other GraphQL server projects will follow them. Until then, we’ve got a strong indication we took the right approach.

GraphQL is just a schema, there are many different implementations of a GraphQL server, AppSync being one of them. I mentioned Apollo server in this series as well.

After some head-scratching, I opened an issue on Apollo Server’s GitHub repository. There, Apollo Server contributor @​glasser shared a helpful suggestion: why not invoke our AuthPlugin from Apollo Server’s context function? Throwing from context would ensure we can control the HTTP status response without having to introduce more methods and error checks to our AuthPlugin (like unexpectedErrorProcessingRequest). With that suggestion in mind, we rewrote our AuthPlugin as follows:

Apollo as a middleware in Express.js, actually.

Apollo Server 3 Cookie Issue #5775

Lastly, instead of writing our API core ourselves, we'll be using the star of this episode --- Apollo Server (a.k.a. GraphQL server). It has detailed documentation available here.