Using tanstack query for caching in rest APIs

[RobinVdBroeck]

Hello,

I wonder if anyone ever used a tanstack query like system for caching (but mostly cache invalidation) in rest apis.

Let's say I've got a simple crud system:

GET /v1/resource/:id
DELETE /v1/resource/:id
POST /v1/resource

The implementing code could than look somelike - in psuedocode:

const queryclient = await createQueryClientWithRedisBackend();

router.get("/v1/resource/:id", ({ id }) => {
   const { data } = await queryclient.useQuery({
      queryKey: ["resource", id],
      queryFn: () => getFromDatabase(id),
   })
});

router.post("/v1/resource", ({ payload }) => {
  const id = await createInDb(payload);
  await queryClient.setQueryData(["resource", id], payload);
});

router.delete("/v1/resource/:id", ({ id }) => {
   await deleteFromDb(id);
   await queryClient.removeQueries({
       queryKey: ["resource", id]
   })
});

Does this have any gotchas I should be aware of?

[TkDodo]

you can’t useQuery on the server, it would need to be queryClient.fetchQuery

[RobinVdBroeck]

I'm just wondering if this is a good idea from an architectural view, not looking for specific details.

I'm mainly wanting to this make it easier to invalidate redis/memcached/... keys, which can be a pain. I'm familiar with react query for frontend applications, and I wonder if I could also use the library for my backend development.

However, I'm afraid tanstack query has given me a hammer and now I see nails everywhere, while I really need a saw.