case study · integrations
ERP Sync Database
The B2B and B2C channels read product, stock and price data straight from the ERP on every request, which both strained the ERP and slowed responses down. I placed a sync database in between: a worker service transfers the data periodically, and the channels now read from that database.
// flow
-
ERP
The source of truth for products, stock and prices; it is no longer queried on every channel request.
-
Worker Service
Pulls data from the ERP at set intervals and writes it to the sync database.
-
Sync DB
A SQL Server database dedicated to channel reads.
-
B2B · B2C
The channels read products, stock and prices from this database instead of the ERP.
// problem → solution → result
- problem
- Channels querying the ERP directly on every request put load on the ERP and slowed responses down.
- solution
- A sync database placed in between: product, stock and price data is transferred periodically by a Worker Service, and the channels read from it.
- result
- The load on the ERP is gone; channel response times improved noticeably.
// technical notes
- Read traffic moved from the ERP to the sync database.
- Because the transfer is periodic, channels may see data up to one interval old; the interval is chosen by how fresh the data needs to be.
- Result: the load on the ERP is gone and channel response times improved noticeably.
// where
- Ersa YazılımSoftware Developer · 2022 — 2025