IT & TechnologyArchive edition6 min read

Choosing an integration strategy for business systems

Connect systems without making each dependent on private details of the other.

Connected infrastructure nodes and concentric paths — Choosing an integration strategy for business systems
Original ARTware computational illustration.

Business applications often grow separately because they serve different groups of people. A catalog describes products in terms useful to a visitor, an inventory tool records quantities present at a location and an administrative application may use its own financial descriptions. Connecting these systems can eliminate repeated data entry and make information available at the right point in a workflow. It can also turn an independent application into one that stops functioning whenever another system has a problem. A sound integration strategy preserves useful independence by defining an exchange around business information and supported operations. Begin by clarifying what is shared, who is entitled to change it and how current an observation needs to be.

Decide who owns a value

Suppose a public catalog needs stock information. The inventory application maintains quantities and their observation times, but the catalog maintains headings, summaries, pictures and display categories. The two applications might already happen to contain a similar product name. That does not make both responsible for changing it. Identify the source whose decision is authoritative for each field being shared. This can prevent an incoming adjustment to a stock quantity from inadvertently replacing the carefully edited public description. A simple data mapping should show the inventory properties the catalog receives, the existing values the catalog keeps and the way both relate their records to the same product. Include any important differences in how units and locations are represented.

Stable identifiers are more reliable than matching records by a display label. Two items may legitimately have similar names, or a catalog editor may make a description clearer without intending to create a new product. Where the systems already use different identifiers, maintain a mapping and specify how new matches are created and verified. A transfer containing an unknown identifier should have an explicit outcome. It might create a draft association for review, be retained as an unresolved record or be rejected with a diagnostic. Silently interpreting it as some existing item can introduce an inconsistency that is harder to notice than a visible failed transfer. Record how entries that are no longer active are represented.

Agree on the meaning of the exchanged information

An integration contract needs to explain more than the names of its properties. An inventory message containing a product identifier, quantity and observation time provides a useful starting point. Is the quantity the number available to sell or the number physically present? Does it include reservations? Is an observation for one location or for a group of locations? If a quantity is absent, does it mean the value is unknown, that the product should be removed or that the source did not change this field? Each answer can affect catalog behavior. Write examples of ordinary values and incomplete or unusual cases. Compare these examples with the decisions made by both application teams rather than treating a sample export as a full description of the agreement.

Related reading: Planning a resilient hosting setup.

Define a way of evolving the contract without forcing both systems to change on the same day. Adding an optional value can be straightforward if the receiver knows what absence means and tolerates fields it does not use. Renaming a required identifier or changing a quantity's unit is more significant. In that situation, it may be necessary to support a revised representation alongside the old one for an agreed period. The systems can then be updated and tested independently. Document how they recognize a supported representation and how they handle something outside that agreement. An explicit compatibility policy reduces the risk of a routine change in one application unexpectedly disrupting the other.

Choose a sensible rhythm for exchange

Some information needs to be obtained at the moment a person performs an action. For example, confirmation that a limited unit can still be reserved may require consulting the system responsible for allocation. A live request is a reasonable choice when using older information would prevent the task from being carried out correctly. It does, however, mean that the requesting activity depends on the receiving service at that moment. Design a useful response to ordinary delays or unavailability. It may be safer to tell a visitor that confirmation is temporarily unavailable than to imply a reservation has been accepted without an appropriate authoritative decision.

Layered flowing curves with fine network-like intersections
ARTware visual study. A complementary computational composition.

Other information is suitable for periodic synchronization. A catalog may retain a recent stock observation for its informational display, updating it regularly and distinguishing the freshness of what it knows. A scheduled transfer can isolate browsing from a brief inventory outage because the public descriptions and last known records remain available. The drawback is delay between a change and its appearance elsewhere. A push-based transfer of changes may reduce that delay while still allowing each application to process information independently. Choose a rhythm according to the consequences of stale data, the expected volume of changes and the team's ability to monitor and recover the exchange. Freshness for its own sake is not a sufficient requirement.

Plan for late, incomplete and repeated delivery

Exchanges rarely behave exactly like their shortest successful demonstration. A connection can be interrupted after the receiver accepts a message but before the sender sees a confirmation. A later transfer can arrive before an earlier one. A data source may temporarily omit a field. The catalog must not overwrite a more recent stock observation merely because it last received an older message. An observation time or defined source version can help determine whether an accepted value supersedes the existing one. Repeated copies of the same exchange should have a predictable effect. An explicit state representation is preferable to inferring delivery status from a lack of visible errors.

Use a clear recovery strategy for missed transfers. Periodic reconciliation can compare a representative set of known identifiers or expected state summaries. If the contract exchanges only changes, define a supported method for obtaining a complete snapshot when the receiver needs to rebuild its information. Record enough transfer metadata to determine what was accepted and what remains outstanding, without unnecessarily duplicating sensitive business records in diagnostic logs. An incomplete export should produce a distinguishable result; it is not equivalent to a complete export that happens to contain zero active entries. Make sure operators can recognize when the public application is displaying older information rather than recent confirmed observations.

Keep the interface narrower than the database

Sharing table access can seem convenient because the data already exists in a queryable form. It also exposes the receiver to private structural choices of the originating application. A later change to how reservations or locations are represented could force the catalog to change even when the information it actually needs has not changed. A supported exchange hides those internal details behind an agreed representation. The source remains responsible for converting its records into the contract. The receiver remains responsible for its local presentation and for combining the exchanged fields with its own records. The boundary can be implemented with an ordinary service interface, a scheduled file or another appropriate supported mechanism.

Test the contract with a small set of representative records before it becomes responsible for routine business activity. Complete an initial transfer, change one known value, repeat a previously accepted transfer and simulate a missed update within the test environment. Include an unfamiliar identifier and a record with absent optional information. Examine the resulting catalog entries rather than relying solely on transmission acknowledgements. Check that the authoritative descriptions are preserved and that an old observation cannot masquerade as a fresh one. Finally, test how a maintainer reconciles their view of the two applications. An integration is useful when it reliably supports the work people do without making every independent change in either application a coordinated overhaul.

Explore the implementation area: IT consulting.