I'm curious why you decided to use Redis instead of consolidating on Postgres. To me the additional surface area of maintenance seems high especially considering most of the time postgres gets you 95% of what you want. Would love to hear a differing perspective. Was it primarily performance reasons? Or perhaps some locking API that postgres doesn't support?
Thanks for the comment and suggestion on Postgres. I agree about the additional surface area of maintenance. However, the reason I used Redis was to become familiar with Redis in the Spring ecosystem. After writing in Python, Go, and Swift, I came back to Java and decided to become a strong Spring & Java developer. That's why I am writing Spring projects to solve different problems with different tech stacks. But now, because you mentioned it, I am interested in using Postgres as a message queue, and I will definitely try it in my future projects.
2 comments
[ 896 ms ] story [ 527 ms ] thread