Notes on warehouse sync.
Field-tested notes on moving data from remote sites to the cloud: offline support, peak seasons, per-site encryption and what a central copy is for.
Adding a fourth warehouse: what it takes to bring a new site onto the central copy
Bringing a new warehouse onto a central copy of your data is real work done by people. Here is the honest setup list, and why each site after the first is easier.
October 10, 2026From nightly exports to a central copy: what changes for a vendor's dashboard
When your dashboard reads a central copy kept current from every customer site, instead of files each site sends overnight, freshness, completeness and recovery all change in ways your users notice.
October 10, 2026One product, many sites per customer
Vendors rarely sell one site to one customer. A separate space per site in one central store keeps each site apart and lets your application add a customer's sites together.
October 10, 2026A support desk that can see the site
When every deployment's current data reaches a central copy within a couple of minutes, your support team can look at a site before calling it and start from facts.
October 3, 2026What your customer's IT team will ask before your service goes on their network
Before a sync service runs inside a warehouse or plant, the IT team will ask what connects where, what is encrypted, and what runs on which machine. Here are honest answers.
October 3, 2026Why a vendor should not build site-to-cloud sync twice
Vendors with technology at customer sites often rebuild data collection for each deployment. Here is what the second and third builds really cost, and what a supported connection changes.
October 3, 2026Per-site encryption keys: why every warehouse gets its own
Giving each warehouse its own encryption boundary limits what one leaked key can expose, keeps rotation a local job, and stops a single weak site from putting every other site at risk.
September 26, 2026What "one IT contact" means in practice for a multi-site rollout
A plain account of the single IT contact a multi-site data rollout needs: what that person does, where their time goes, and why one named owner moves faster than a committee.
September 26, 2026Why nightly exports are the wrong shape for multi-site reporting
A nightly export shows head office every site as it stood yesterday. We look at what that delay costs, and why a central copy current to within minutes changes the work.
September 26, 2026How to centralize warehouse data from every site without replacing what runs the warehouse
A small service beside each warehouse database sends changes outward to one central copy. The head office gets one view of every site; the warehouse floor keeps the system it already trusts.
September 25, 2026Why reports should never run on the warehouse database
The operational database exists to run the floor. Every report that queries it competes with picking, packing and shipping. A central copy takes that load away and leaves headroom for peak.
September 25, 2026What offline support really means when a warehouse loses its link
Changes queue on site, compressed and encrypted, and resume table by table when the link returns. Delivery is at-least-once, so nothing is lost. Here is exactly what is and is not promised.
September 25, 2026One report across time zones: getting the clocks to agree
Sites in Eastern, Central and Pacific time each keep their own clock. A central copy, stamped by site and current within minutes, gives head office one consistent day, shift or peak.
September 25, 2026The true cost of a cloud copy of your warehouse data, and the cheaper shape
A cloud relational database sized for every site is the expensive shape. Low-cost document storage, fed only with changes over ordinary internet links, is the cheaper one. Here is why the shapes differ.
September 25, 2026What a design partnership looks like for a logistics company: one site first
Who qualifies, what the first site involves, who drives the rollout, how sites and tables are added, and how the contract and subscription work. A plain account of partnering with redfly.
September 25, 2026Outbound only, encrypted per site: how warehouse data leaves the building safely
The sync service opens outbound connections only, compresses and encrypts each site's changes with that site's own key, and keeps each site in its own central space. What a security reviewer will ask.
September 25, 2026Peak season for warehouses: why headroom matters more than horsepower
On Black Friday the warehouse server has no room to spare. Moving reports off it, with a sync service that throttles itself when the site is busy, buys the headroom that keeps the floor steady.
September 25, 2026Ten billion rows over the public internet: what we learned
We have kept more than ten billion rows in step across ordinary public internet links, not dedicated lines. Here is what held up, what did not, and what surprised us.
September 25, 2026IoT and fleet telemetry: high writes, flaky links, millisecond reads
Devices and vehicles write constantly over links that come and go, while the operations screen needs the latest state in milliseconds. How we split the two jobs.
September 25, 2026Drift, backfill and recovery: the unglamorous parts of sync
Copies of data quietly disagree, restarts lose their place, and schemas change under you. What drift is, how it happens, and how an honest sync service detects and repairs it.
September 25, 2026SQL Server change tracking: why we read changes on a short interval
SQL Server offers two ways to learn which rows changed. redfly uses the lighter one, change tracking, and reads it on a short interval. Here is why, and what it means for freshness.
September 25, 2026PostgreSQL logical replication as a cache feed
PostgreSQL can publish every row change as a stream. redfly subscribes to that stream to keep Redis in step. What publications and replication slots are, and what to watch in operation.
September 25, 2026MongoDB change streams as a sync source
MongoDB change streams deliver inserts, updates and deletes as they happen. redfly uses them to keep Redis, or a central store for site sync, in step, and to resume cleanly after an interruption.
September 25, 2026Your warehouses, your data, one view.
Start with one site and see it working before you commit to anything wider.