How should one update a Redis cache in a CRUD application?

Question

I'm making a CRUD application that uses PostgreSQL as the primary store and uses Redis as a cache. For this part of the application, the API pulls all its data from the Redis cache.

This has worked fine for reading from Redis, but now I want the changes that are committed to the database during a create/update/delete to be immediately reflected in the Redis cache. I'm unsure about how to do this, or if this is even the best way to do it.

Could someone please provide an example of how to achieve this?

e4c5 · Accepted Answer · 2015-08-30 03:25:02Z

2

First of all it's largely unnecessary. A well designed PostgreSQL database is fast and there is no need to arbitrarily cache every single query. You have have certain queries that are slow and cannot be optimized, you can cache them into redis at the application level as you know.

If you insist on caching everything you need foreign data wrappers available since postgresql 9.3. On that page you will find links to two redis FDWs. You will still need to write a hell of a lot of triggers.

answered Aug 30, 2015 at 3:25

e4c5

53.9k11 gold badges110 silver badges139 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

m0meni Over a year ago

Thank you so much. I'm very new to the backend, and I've been obsessing with performance. I really was hoping to get an answer like this telling me that I was looking at it the wrong way.

Collectives™ on Stack Overflow

How should one update a Redis cache in a CRUD application?

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related