What does HackerNews think of message-db?

Microservice native message and event store for Postgres

Language: Shell

#23 in PostgreSQL
Show HN: Light implementation of Event Sourcing using PostgreSQL as event store | Oct 2023
In addition to the alternatives mentioned, here’s another Postgres-only ES implementation: https://github.com/message-db/message-db
Event Sourcing (2005) | Aug 2021
Check out MessageDB https://github.com/message-db/message-db. It's basically Postgres and can be installed into any Postgres DB.
Building a Distributed Turn-Based Game System in Elixir | Apr 2021
Expand Context ↕
Trying a new language or framework is fun experiments that you spend a few hours on. I have been enjoying implementing Message DB[0] in a hobby project. My current job is not in programming, and not looking for one.

[0]https://github.com/message-db/message-db
Why Segment Went Back to a Monolith | Apr 2020
Expand Context ↕
Like others have mentioned here, simply pointing out examples where microservices have failed doesn't imply that microservices can't succeed. I've attempted to bake bread twice and they both failed. I didn't conclude that baking bread can't be done, but that my skills to do it were insufficient.

There are lots of examples of successful companies using microservices, but I believe the real problem is in defining what constitutes a microservice. Most people call things "microservices" that are nothing of the sort. I can unequivocally say if you built a "service" that depends on other things being 100% available (like another "service") than you haven't built a microservice (ie: those things you built shouldn't be called services).

By that token, autonomy is a pretty important factor. The Udi Dahan teachings (https://particular.net/adsd) (currently available for free) promote this style of architecture. A concrete example of a toolkit for building true microservices can be found in Message DB (https://github.com/message-db/message-db) and/or Eventide (http://docs.eventide-project.org/)

I wouldn't suggest, however, that anyone can just watch the course, pick up these tools and succeed. Like baking a good loaf of bread, it takes a lot of skill, work and experience. Whether or not you succeed at building microservices is ultimately up to you and your team.