Remember the ABC when you are going to integrate computer systems. The ABC of System Integration is about the where, how and what of integrating systems, most of the time on a service level.
Let’s break this down
Let’s break this down and clarify the ABC of systems integration.
A stands for the Address. The address is all about the location of the service. The A of address tells you where exactly the service is located and where you can find it. Since the vast majority of the services are being known and built as webservices. Mostly you will see webservices being hosted using HTTP(s)
B stands for the Binding. Binding says something about the protocol that you use to make the integration possible. In simple words: this is the language that the client and the service use to talk with each other. The default way to access the webservice is through HTTP(s) based protocols like: REST and plain old SOAP. However? Be very careful to make the very wrong assumption that it’s only possible to integrate using SOAP and REST. Because you can virtually use any protocol to integrate ranging from application web-protocols like: REST and SOAP but also messaging protocols like AMQP and the famous file transfer protocol FTP. It’s even possible to integrate on a database level, but this is a huge anti-pattern.
C stands for the contract. It’s the interface “you talk to”. The contracts (mostly) defines the data format of the methods being exposed by the service. It’ the agreement between the two systems in which data format the data is transferred. The structure of the data is mostly described in JSON, XML, CSV but also Objects (like in C#)
To summarize: Keep your ABC on point. Address, Binding and Contract.