What you get
- A REST or GraphQL API in front of your systems, so partners and tools never need to know how they work inside
- Webhook handlers, so a change in one system shows up in the others within seconds
- Retries and an audit log, so an outage at a partner delays an update instead of losing it
- Mapping and validation between formats, so bad data is stopped before it spreads
How it works
- Discovery. Which systems, which data moves where, and what should happen when something fails.
- Build. The integration built against test accounts, with weekly written updates.
- Ship. Switched on with monitoring, so failures are seen by a person instead of discovered by a customer.
- Handover. Documentation of every flow, and the code in a repository you own.
Technology
TypeScriptREST & GraphQLWebhooksCloudflare WorkersSupabaseAWSAzure
Related work
Common questions
What happens if one of the systems goes down?
Events wait and are retried with increasing gaps, so an outage becomes a delay rather than lost data. Anything that still fails is surfaced for a person to resend or resolve.
Do you work with REST and GraphQL?
Yes, both, along with webhooks for systems that push changes as they happen.
Where does the integration run?
Usually on Cloudflare Workers, which scale with the traffic and cost almost nothing when quiet. When your systems already live on AWS or Azure, it runs there instead.
Start a project
Describe the problem in a few lines and I'll reply with questions, not a quote. I'm based in Auckland and work remote-first, so it doesn't matter where in New Zealand you are.