Sitemap · Learn
Patterns
Architecture patterns for connecting an ERP, a store and a bank: when to use each, when not to, how it fails, and how ERPNext does it.
6 pagesUpdated 14 Oct 2026All sectionsXML version
- Point-to-point vs a hubPoint-to-point integration builds one connection for every pair of systems, up to n(n−1)/2 for n systems, while a hub gives each system one connection to a shared layer, so n systems need n./patterns/point-to-point-vs-hubUpdated 14 Oct 2026
- Webhooks vs pollingA webhook sends one request for each change and arrives when the sender decides, while polling sends a fixed number of requests a day and waits up to one interval, so the cheaper choice depends on how many changes arrive against how many polls fit inside the delay you can accept./patterns/webhooks-vs-pollingUpdated 14 Oct 2026
- Idempotent webhooksAn idempotent webhook handler records each event's unique id in the same transaction as its effect, so receiving the same event any number of times changes the books once./patterns/idempotent-webhooksUpdated 14 Oct 2026
- Transactional outboxA transactional outbox saves each outgoing event in a table of the same database, in the same transaction as the business change, and a separate relay publishes it afterwards, so the event exists if and only if the change was committed, at the cost of delivering at least once./patterns/transactional-outboxUpdated 14 Oct 2026
- Eventual consistency in stockEventual consistency in stock means each sales channel holds its own copy of the count and learns of other channels' sales only after a sync lag, so two orders for the last unit can both be accepted unless one place decrements the stock when an order is taken./patterns/eventual-consistency-in-stockUpdated 14 Oct 2026
- Reconciliation as a jobA reconciliation job compares what the books say with an outside record, such as a bank statement or a gateway settlement list, on a schedule, and leaves a short list of differences for people to resolve./patterns/reconciliation-as-a-jobUpdated 14 Oct 2026