It's a common architecture to have PostgreSQL and Redis serve as the backbone of your app, but PostgreSQL may be capable of everything you use Redis for.

roni

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Redis is often used for job queuing, distributed locking, and pub/sub mechanisms in web services. However, PostgreSQL has features like `SKIP LOCKED`, advisory locks, and the `LISTEN/NOTIFY` statements that can achieve these tasks effectively. This can help simplify your architecture by using just PostgreSQL and reduce operational costs associated with maintaining multiple data services.

Do You Really Need Redis? How to Get Away with Just PostgreSQL

<p>This is great, but can you find out any frameworks or services that could be used with these features of Postgres? Or do I have to write everything from scratch? Then Redis support is not so costly, no?</p>
