apollo-cache-persist VS graphql-shield

Apollo client comes with an in-memory cache which can be persisted to various storage providers with an additional official library. Obviously not as easy as relying on browser caching, but there are lots of options available. I often find myself having to disable client-side response caching anyway, as most of the data for the sites I work on needs to be as up-to-date as possible.

Yes they have but using key value storage https://github.com/apollographql/apollo-cache-persist, for better performance use mmkv instead of async storage

I did find https://github.com/apollographql/apollo-cache-persist however, but I've never used it so can't tell you much about it.

- https://github.com/dimatill/graphql-shield/issues/988 - https://github.com/dimatill/graphql-shield/issues/1485

Second a NextJS app is deployed to Vercel containing a GraphQL server function. This is an Apollo server that consumes the halo-graphql package using GraphQL Modules. The server also implements caching and rate limiting using GraphQL Shield.

GraphQL Shield is a great tool for creating authorization layers that has vast adoption from the community. In fact, GraphQL AuthZ is highly inspired by GraphQL Shield! However, GraphQL Shield uses a different approach compared to GraphQL AuthZ for applying authorization rules.

Haven't used it yet but GraphQL Shield looks pretty good. https://github.com/maticzav/graphql-shield

You can also use libraries like GraphQL Shield which offers powerful middlewares to do this. But remember that authorization does come with attached cost since you are running a specific logic in/before your resolvers for all the fields which you want to authorize.

Try graphql-shield