Reports that slow down as a logistics company grows

Heavy reports slow down the system dispatchers use all day. Fixing the slowest reports and giving reports their own copy of the data come before buying a big analytics platform.

1 min readMade-up stories, not client work

Scalability: story 12 of 15

A made-up story

Picture a trucking company. Dispatchers use one system all day, and managers run big reports on the same system every morning.

What's going wrong

When the reports run, the dispatch screens freeze. Someone suggests buying a full analytics platform.

What they have today

  • One database for dispatch and reporting
  • Years of shipment history
  • A reporting tool the managers like

What we can't ignore

  • Dispatch can't slow down
  • Reports must stay accurate
  • Budget for a big new platform is uncertain

The choices

  • Worth a look

    A bigger database server

    Helps for a while, at a higher monthly cost.

  • Our pick

    Fix the slowest reports, and give reports their own copy

    Reports read from a copy, so dispatch never waits.

  • Maybe later

    A full analytics platform

    Worth it once reports need data from several systems.

What we'd do

Start with the slowest reports and fix how they look up data. Then add a read-only copy of the database just for reports, and point the reporting tool at it. Move old shipment history into an archive.

Why

  • Dispatch stops waiting on reports
  • Managers keep the tool they know
  • Spending stays small until there's a real need

Where the money really goes

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

Fixing reports costs some developer time. A read-only copy adds a monthly fee. Both cost far less than a new platform and the work to adopt it.

Developer time
A few days on the slowest reports.
Database copy
A second, smaller monthly fee.
New platform
Licences, setup and training, if it's ever needed.

Running, growing, and staying safe

If something breaks

If the report copy has a problem, dispatch keeps running.

When it grows

More history goes to the archive, so everyday screens stay quick.

Keeping it safe

Reports read from a copy that can't change real data.

What the business gets

  • Dispatch screens that never freeze
  • Faster reports
  • No big new system to buy

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

When we'd look again

If reports need data from several systems, or history outgrows the copy, an analytics platform becomes the right next step.

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: Getting an oversized cloud bill under control

A software company's cloud bill grew faster than its customers. Cleaning up comes first; long-term discounts come only after, and only for the steady part.

Read the next story