data.day
risk-management / infrastructure / offline-first

Cloud Dependency Is a Cost, Not a Convenience

We rented our infrastructure. Then the internet went down. The crew stood still. The cloud is a landlord. You need to own your operations.

Ingrid Pipeline Ingrid Pipeline

The Silence of the Server

The warehouse was buzzing. Forklifts were moving. Trucks were waiting at the bay. Then, the screens went black. Amazon Web Services (AWS) had a regional outage in Virginia.

The scanners stopped working. The inventory system would not load. The drivers could not print their manifests. The warehouse manager stood on the loading dock. He watched twenty drivers turn off their engines. “We can’t load,” he said. “The system won’t let us.”

They waited four hours. That is eighty man-hours of driver time. That is four hours of delayed shipments. That is penalties from the customers.

The internet came back on at 2:00 PM. But the day was lost.

The Fragile Link: The Tether

We have accepted a lie. The lie is that “Always Online” is acceptable for physical work. It is not. When you build an app that requires a constant connection, you are putting a leash on your workforce. The leash is as long as the WiFi range.

If the leash breaks:

  • The app freezes.
  • The data is lost.
  • The worker waits.

This is Fragile. It introduces an external dependency that you cannot control. You cannot fix AWS. You cannot fix the cell tower. You are helpless.

The Sturdy Fix: The Battery Model

Think of data like electricity. Devices used to be plugged into the wall. Now they have batteries. The battery lets you work when you are away from the plug.

Software needs a battery. That battery is the Local Database.

We rebuilt the warehouse app. Now, the inventory list lives on the scanner.

  1. Morning: The scanner syncs. It charges its “Data Battery.”
  2. Day: The internet goes down. The scanner does not care. It has the data locally. The driver scans. The inventory updates on the device.
  3. Evening: The internet comes back. The scanner flushes the data to the cloud.

The outage in Virginia did not matter. The warehouse kept moving. We decoupled the operation from the connection.

Risk is Cost

Operations Directors look at the cost of software licenses. They rarely look at the cost of downtime. A cheap, web-based app costs $10 per month. An offline-first, native app costs $50 per month.

But one outage costs $10,000. Do the math. Reliability is not an upsell. It is insurance. Pay for the plumbing that works when the water pressure drops.

FAQs

But isn't the cloud more secure?

The cloud is secure for storage. It is risky for access. If you cannot reach the bank, it does not matter how safe the vault is.

Local storage is hard to manage.

It used to be. Modern mobile databases (like SQLite) are robust. They manage themselves. They are standard plumbing.

What happens if the device breaks?

You sync often. The data is on the device only for the 'gap' between syncs. The risk is small. The risk of downtime is large.