2021 integration & API management predictions
The year 2020 showed that organizations which had invested in integration & APIs were the ones that were resilient enough to pivot and survive.
The year 2020 showed that organizations which had invested in digital transformation were the ones that were resilient enough to pivot and survive.
Integration and APIs are two sides of the same coin, and digital transformation cannot happen without them. Without them, all you have is a collection of systems and silos of data. This is why integration and APIs have suddenly become the most important elements in digital strategy plans for 2021.
Here are my predictions for integration in 2021:
Compose, don’t create
According to Gartner, by 2023, over 50% of medium to large enterprises will have adopted an LCAP (low-code application platform) as one of their strategic application platforms. Instead of high-end developers writing applications from scratch, less technical users will be composing them. “Citizen developers” will have model-driven solutions for orchestrating app integrations and composing applications.
B2B integration and MFT marry in the cloud
B2B integration, an unseen but critical part of business, was reborn in the cloud in 2020. New ecosystems and marketplaces using technologies like APIs brought new life to traditional partner interactions. Now managed file transfer (MFT) is ready for its own transformation. The ugly truth is that on-premises file transfers are still part of critical business transactions for many. But MFT is ready to move to the cloud with B2B integration as businesses rethink the way they communicate and share data.
Getting from data to value faster
Data integration and application integration will come together with analytics more closely tied to integration. Traditionally data integration which is “integration for the purpose of driving analytics” has been kept separate from application integration since the former is more batch oriented while the latter is real time. A modern integration strategy brings both needs together within a cloud data hub – an iPaaS that serves as the point of collection and distribution of data for analysis and reporting within cloud data warehouses and data lakes. This turns data into business value faster. The proliferation of SaaS applications in the cloud has made it more difficult to create a coherent view of distributed customer data, but the Open Data Initiative (ODI) will step up with a common standard.
API management rules the mesh
With the rise of microservices, IT leaders are looking at service mesh technology to manage network-level communication. And with dozens of service meshes on the market, a new standard has emerged as a vendor-agnostic interface; the Service Mesh Interface (SMI). At the same time, businesses are implementing multiple API gateways for different use cases, and there’s a need for a single API control plane to serve as the master for all gateways. API management will take on APIs, microservices, and service meshes, providing a single platform for full control of all the elements of cloud-native applications.
Hybrid is [still and always] best
While the balance of enterprise systems tips further into the cloud, hybrid remains the optimal operating model in the future. Instead of losing momentum, the hybrid integration house getting larger. It needs to accommodate:
- More types of users, ranging from highly technical to business oriented
- More domains, extending from application integration to B2B integration, event-based integration, and of course API and data integration
- More endpoints, with mobile and IoT increasing at a dramatic rate
- More deployment models, including multi-cloud integration and embedded as well as the more traditional on-premises/cloud hybrid.
These hybrid integrations will be able to be developed anywhere and deployed anywhere.
API portals lose their heads
API portals are going headless. Businesses want to expose APIs as products in a “digital brochure” that uses their branding and their own UI technology. And APIs are not the only asset users want to put in a developer portal; often they want to capture microservices and services related to those APIs. Headless portals allow them to surface APIs and related assets in custom portals.