Use APIs to Integrate
API-led connectivity enables the reusability of the integration flows within
multiple parties. Also, the integration flows can be reused inside the
integration platform. Due to the reusability factor, it helps the developers to
build their logic rapidly and efficiently, thus reducing the overall turnaround
time (TAT). It makes the development process almost 3 times faster and
reduces the integration cost by almost 70%.
In the API led architecture, the IT infrastructure has three distinct API layers:
System Layer: In the System layer, various system APIs reside (e.g. for ERP,
CRM, SAAS Applications, etc.). Using the system APIs, these systems can
be accessed. The data residing in these systems gets exposed by these
System APIs in a secured manner.
Process Layer: The next layer is process layer where the orchestration
activities of various data such as aggregation, join, splitting, etc. are done
by calling multiple System APIs. For example, an Order Fulfilment Process
API can call systems APIs of the ERP, CRM, Order Management System,
etc. Thus, if any business user or developer wants to Use the order
management functionality or related data, he or she can directly use the
Order Fulfilment Process API, rather than building everything from scratch
using the individual System APIs.
Experience Layer: These are the top-most layer which should be exposed
publicly for consumption. Experience APIs are the means by which data
can be reconfigured easily to meet the needs of multiple audiences. In
addition, the unnecessary methods can be removed and only the
necessary methods can be exposed in Experience APIs in a simple way.