API Management
01
Why need APIM?
MSA Uptrend
SOA Downtrend
ESB Downtrendp>
API Gateway uptrend
Source: Google Trends
Various companies around the world are focusing their attention on APIs to make their business successful.
APIs are being introduced to create a more flexible business environment, and according to Forrester Research, the world's top 3 IT industry research firm, 40% of all companies in the United States are investing in API Management.
02
API Management
The most critical components when establishing microservice architecture is the API Management System and the API Gateway. API Management is a Middleware, the advanced API Management System compared to the Enterprise Service Bus(ESB) of SOA, that interlocks all End Points for API at the front of various APIs like proxy servers and provides several additional functions.
API Management is the intersection of API users and API providers. In other words, API management is a set of processes that gives business control and visibility to the applications and data connections through a variety of APIs. The ultimate purpose of API management is to monitor the lifecycle of the APIs and to ensure that APIs (which are used by developers and applications) to work appropriately meeting their needs.
The most critical components when establishing microservice architecture is the API Management System and the API Gateway. API Management is a Middleware, the advanced API Management System compared to the Enterprise Service Bus(ESB) of SOA, that interlocks all End Points for API at the front of various APIs like proxy servers and provides several additional functions.
Tetra Wing is BMtech System's most important API Management Solution in microservices. It is the Integrated Management Platform that interlocks and integrates all solutions including Hardware Layer, OS Layer, Orchestration Layer, API Management Layer, and Visualization Layer.
03
Layered Approach Case for API Management
One of the reasons why you need API Management is, "Integration." Users (Consumers) that use API can be defined as Mobile, Chatbots, Enterprises, Web Applications, Smart Watch, Middleware, IoT landscape & devices, where API endpoints can be SaaS applications, Mainframes, FTP files servers, Databases, Web Services, Legacy Systems, Legacy Applications, or etc.
The most demanding task for most clients is to perform protocol conversions when integrating the legacy system.
Central IT team controls System APIs. LoB Dev or IT Development Team controls Process APIs including orchestration, composable APIs, and Microservices. Lastly, The App Development Team controls the Experience APIs. Hence, implementing the Layered Approach clarifies the accessibilities and roles.
Central IT Team possesses the ownership of System APIs, and LoB Dev or IT Development Team has the right for Experience APIs which clarifies the accessibility and ownership.
Process APIs :- Processing layer will perform Orchestration and helps to process the API gateway core functionalities like authentication, authorization & required functional business layer. System APIs :- System APIs layer refers to legacy modernization, connectivity to SaaS Applications, web services & Rest APIs. Experience APIs :- This layer is a purpose built to test the API mocks and exposed to Developer Portal
04
Future of APIs
Jeff Bezos
CEO of Amazon
Amazon’s API Mandate
· All teams will henceforth expose their data and functionality through service interfaces.
· Teams must communicate with each other through these interfaces.
· There will be no other form of inter-process communication allowed : no direct linking, no direct reads of another team’s data store, no shared-memory model, no back-doors whatsoever. The only communication allowed is via service interface calls over the network.
· It doesn’t matter what technology you use.
· All service interfaces, without exception, must be designed from ground up to be externalize-able. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions.
“Anyone who doesn’t do this will be fired. Thank you; have a nice day!”
Everything API
“API First”
