DEV Community

Discussion on: Zero dependancy Pub / Sub system with PostgreSQL

Collapse
 
acoh3n profile image
Arik

I like this idea quite a bit. We actually have a postgres based setup at work plus a rabbitmq and it would be nice to try to eliminate a moving piece (rabbit) if I can. I love rabbit but I love minimalism even more. The only disadvantage I can think of is giving all the nodes access to the database which I may not want to due to security considerations.

Collapse
 
skatkov profile image
Stanislav(Stas) Katkov • Edited

You can create a dedicated database user that has access to certain tables.

Collapse
 
_gdelgado profile image
Gio

Agreed, opening up access to all nodes is a serious drawback to this approach but I am sure that there are ways to go around this.

How are you and your colleagues liking RabbitMQ. We too are big fans of minimalism. Have there been some unexpected downsides to to introducing rabbit (besides having an additional moving piece)?

Collapse
 
theodesp profile image
Theofanis Despoudis • Edited

Why don't you use a Redis task queue to see how it goes?

Collapse
 
acoh3n profile image
Arik • Edited

I'm a big fan of rabbit. Used it in production on several occasions for rather large (hundreds of messages per second) deployments and it worked really well for me. It's very easy to setup and it just sort of works.

Collapse
 
bgadrian profile image
Adrian B.G. • Edited

Minimalist would be a simple Redis, like other said. You can get also persistent storage (from time to time), performance and scaling (if needed).

Slack devs are also reticent to new dependencies and avoids adding new tech in their stack, you can read about their Job Queue system here, which is exactly what you need too (more or less). The old system is on redis (previous version, probably is enough for your needs)