Integration debt: how five “simple” connectors become a night shift
3 May 2026
Custom web applications in wholesale and field-service companies often grow one connector at a time. Each supplier promise sounds modest: a CSV drop, a webhook, a nightly pull. Five years later the night shift belongs to whoever understands the collision order.
What we look for in a health review
- Overlapping jobs that write the same stock or customer fields
- Silent retries that mask upstream failures
- “Temporary” transforms that became permanent business rules
- No single place to answer “which feed won last night?”
A repair order that usually helps
Rather than rewriting every connector, we often recommend a single ingestion boundary: one module that accepts external payloads, validates them, and publishes internal events. Existing connectors become adapters behind that boundary. High-impact feeds move first; low-risk feeds wait.
This is not glamorous work. It is the difference between an application staff trust and one they route around with clipboards.
If your team is arguing about which brittle job to touch first, a LeafHub architecture health review is built for that triage.