问HN：什么时候需要使用账本运行时而不是数据库？
我正在为后端系统开发一个确定性的双重记账运行时，因为在这些系统中，财务准确性至关重要。
实际上，许多团队开始时使用普通数据库和应用层的会计逻辑。但在某个时刻，重试、竞争条件和对账问题会出现。
我很好奇这里的工程师是如何决定的：
— 什么时候普通数据库不再足够？
— 什么信号表明会计逻辑应该迁移到专用的账本运行时？
— 你们是否经历过一些事件，确定性重放或可审计性本可以提供帮助？
我希望听到工程方面的看法，而不是产品讨论。
查看原文
I'm working on a deterministic double-entry ledger runtime
for backend systems where financial correctness matters.<p>In practice, many teams start with a regular database and
application-level accounting logic. At some point, retries,
race conditions, and reconciliation issues appear.<p>I'm curious how engineers here decide:
— when is a plain database no longer enough?
— what signals that accounting logic should move into a dedicated ledger runtime?
— have you experienced incidents where deterministic replay or auditability
would have helped?<p>Looking for engineering perspectives, not product discussion.