Hosting an internal operations app for a manufacturer

A factory's scheduling app lives on an old server in a closet. We compare a new server, a straight move to the cloud, and handing the running of it to managed services.

2 min readMade-up stories, not client work

Cloud Hosting: story 3 of 15

A made-up story

Picture a factory whose production schedule runs on a custom app built years ago. It sits on one aging server in a closet next to the break room.

What's going wrong

If that server dies, the factory can't schedule or ship. Backups go to a drive nobody has tested, and the person who set it up has left.

What they have today

  • One aging server running the app and its database
  • Label printers on the factory floor that print from it
  • A single internet line

What we can't ignore

  • Shipping can't stop for more than a short time
  • The factory's internet isn't perfect
  • A small IT team with many other jobs

The choices

  • Worth a look

    Buy a new server and keep it on site

    Familiar and quick, but the same single point of failure in a newer box.

  • Worth a look

    Copy the server as-is into the cloud

    Gets it out of the closet, but someone still has to patch and back it up.

  • Our pick

    Managed app hosting plus a managed database

    The provider handles updates, backups and a standby copy of the database.

  • Not for them

    Rewrite the app as many small services

    A big, risky project for an app that works fine.

What we'd do

Move the app to a managed hosting service and the database to a managed database with automatic backups and a standby copy. Add a second internet line, and keep a small local service for the label printers so a short outage doesn't stop shipping. Test a full restore before switching over.

Why

  • Backups and updates stop depending on one person
  • A second line and a local printer service keep shipping going
  • The app itself barely changes

Where the money really goes

No prices here: this shows where the costs sit, not what they'd be for any real business.

A new server is a one-time purchase, but the hidden cost is the upkeep and the risk. Managed services cost a monthly fee and remove most of that upkeep.

Hardware or hosting
On site: a server every few years. Managed: a monthly fee.
Upkeep
On site: patching, backups, repairs. Managed: mostly the provider's job.
Downtime
Every hour the schedule is down, the floor waits.

Running, growing, and staying safe

If something breaks

A standby database takes over if the main one fails, and a tested restore proves the backups work.

When it grows

A second plant can use the same app without new hardware.

Keeping it safe

Automatic security updates and limited access replace an unpatched server in a closet.

What the business gets

  • No more single box holding up the factory
  • Backups that have actually been tested
  • A small IT team freed for other work

These are the kinds of results the approach aims for, not measured results.

When we'd look again

If the factory's internet stays unreliable even with two lines, we'd look again at a modern on-site server with backups to the cloud.

If you liked this, read

About these stories. These stories are made up to show how we think. They are not client projects, describe no real business, and contain no measured results.

Next: Moving a design studio off its office file server

Huge project files and an ordinary office connection make moving everything to the cloud painful. A mix of local and cloud storage keeps work fast and gets backups out of the building.

Read the next story