Hacker News Reader

Why is something that should be a library over an ORM or other data store now a service product?

Thanks for the question! My view is that when you are creating a product and there is something that can get you faster at delivering your core value to your customers, it makes sense to leverage it.

From past experiences, on a reasonably big company (>100 engineers) that needs to do these money movements checks, it would save at least 3 engineers from support/evolution and not counting the development time for a good ledger.

From my experience as running my own SaaSes, I'd rather have a library over an ORM, or a self-hosted service. Having yet another cost to manage, another API to monitor, and an unreliable interface (HTTP over internet), just isn't worth the cost.

That is very interesting to hear. I would love to better understand the kinds of problems you may have faced with these systems.

On the cost side, the goal is to charge on average 1/10 of what you currently spend, so cost is actually a feature. I'm working on a self-hosted version for some customers that are asking for it, but not due to reliability of HTTP over the internet, I would love to hear more about this. Can we chat?

Reply on news.ycombinator.com