System integration is done by contract
Opening a connection is not integration. A bridge built without field, direction, authoritative source, and failure behaviour moves conflicting records faster.
· TankDev Mühendislik
‘Let’s connect the systems’ sounds like a technical scope. Often it only opens a channel: an API key, a file drop, a webhook. There is a channel. There is no contract.
System integration is not a channel. It is the rule of a data flow. Systems connected before the rule is written multiply authoritative-source ambiguity at production speed.
What the contract holds
An integration contract fixes four things. Source and destination. The fields that move, and their types. Direction: who writes, who reads. Failure: timeout, duplicate message, rejected record.
- Which entity does this flow carry?
- What happens if the same message arrives twice?
- If the other side returns 500, which state does the operation stay in?
No bridge without a boundary
If system boundaries are unclear, a contract cannot be signed. Each system treats its own record as the original. The bridge does not reconcile two originals. It hides the contradiction by showing both as current.
The right order is entity and authority, then contract, then channel. The reverse produces structures that are declared ‘integrated’ while the reports do not match.
What is delivered
A working transfer, a record of every run, and a rejection the operation can see. Documentation includes the field list and the direction. That delivery comes before a demo screen.
If current software will not accept that contract, a record layer is needed in between. That layer is usually custom software.
If the systems to connect and the records that must move are known, a draft contract can be discussed. Get in touch.