Design an idempotent double-entry ledger service
Design a ledger service that records money movements for merchants as double-entry transactions and answers balance and history queries. Cover the data model, making writes idempotent so a retried request is never recorded twice, keeping balances correct under concurrent writes, and scaling the service as volume grows.
No answer yet. Write the first one; the best answer gets endorsed.
