- Articles
- 7
- Category
- Technology
- 10 September 2026When to use an orchestrator and when to write codeA workflow tool and a service solve the same problems differently. Four criteria that settle which one a specific process needs.
- 9 September 2026Deciding which system owns which fieldA sync cannot resolve conflicting business rules on its own. Decide who can write each field before connecting the systems.
- 8 September 2026Dead letter queues, and why silence is the worst failureA failed integration needs a visible recovery path. Retry budgets, failed work queues and reconciliation prevent errors from disappearing into logs.
- 7 September 2026Integrating with a system that has no APIExports, database replicas and file exchange are all workable. Screen scraping usually is not, and here is how to tell the difference.
- 5 September 2026Webhooks done properlyReceiving webhooks is easy. Receiving them so that duplicates, replays, out of order delivery and outages do not corrupt your data takes six specific things.
- 3 September 2026Building an API other people will useAn internal API that becomes a partner API exposes every undocumented assumption. What to settle before the first external caller.
- 23 August 2026Reconciliation: the job that runs when nothing is wrongScheduled comparisons can find missing or inconsistent records even when no request reported an error.
Let’s talk about the system you need.
Tell us where the current process breaks down. We can map the workflow, examine the integration requirements and define a practical scope for the build.
- A mutual NDA is signed before project details are shared.
- Scope is fixed in writing before any build starts.
- You own the source code, the IP and the documentation at delivery.
- Support plans are available and tailored on a discovery or technical call.