BENEFITS OF API-CENTRIC INTEGRATION
A fine-grained and modular system design, in which all systems interact via well-defined APIs, offers a range of key benefits:
- Avoids central bottlenecks with distributed integration based on smart endpoints
- Reuse of well-defined interfaces (APIs) across modularized systems
- Scales on demand
- Provides services dynamically and API discovery
- Provides APIs via self-service developer portals
- Centralizes API catalog and documentation
- Exposes APIs internally and externally to address different API consumer segments with different API policies
- Integrates with single sign-on (SSO) or identity provider solutions
- Implements consolidated, consistent, and controlled security and access model
With API-centric integration, service providers have the foundation for effective asset monetization and partner ecosystem establishment.
SERVICE PROVIDER SUCCESS WITH RED HAT AGILE INTEGRATION
Red Hat’s agile integration solution addresses integration challenges and provides the previously described benefits via APIs and API management. Agile methods and practices are combined with specific technologies to produce a flexible, adaptive, and reusable platform for rapid application and data integration, as well as integration of OSS and BSS, with legacy systems.
This agile integration solution outlines three pillars: distributed, containerized, and API-based integration. These three pillars translate into concrete capabilities for communications service providers:
- Distributed integration increases communications service provider flexibility
- Containers increase scalability
- Managed APIs increase reusability
The agile integration solution from Red Hat unites legacy systems, OSS and BSS, and network systems with internal and external end-user applications. Components of this solution are included in all areas of a typical telecommunications stack.
The agile integration pillars translate into an effective reference architecture for service providers.
This reference architecture is organized into several key functional areas:
- API microgateways that interface with internal and external channels via shared or dedicated gateways, aggregating thousands of integration points from the back end.
- Lightweight mediation that offers composition, integration, and transformation functionalities.
- Mediation logic can be broken up into standalone integration components that can be distributed, deployed, and scaled on demand.
- The mediation layer is between the gateways and the actual microservices or back ends.
- Microservices that interface with the mediation layer and are separate from legacy architecture—enterprise application integration (EAI) and service-oriented architecture (SOA).
- Functionality that is shared with the legacy architecture for operational purposes, including logging and monitoring, can reside in containers.
- Microservices provide new back-end functionality and can replace specific BSS or OSS functionalities.
- Messaging that can be used to interconnect various components, enabling high-speed, asynchronous communication with reliable delivery.
- Real-time messaging is built for high-throughput streams, fault tolerance, and horizontal scalability and supports geographically distributed data streams and stream processing applications.
- Operations functions that include service discovery, service catalogs, and life-cycle management and automation.
- These functions interface with the API microgateway to provide shared functionality. Microservices can take advantage of this shared functionality through mediation.
- Business process automation is an optional, compatible capability.
These functions are containerized and certified for Red Hat® OpenShift® Container Platform. OpenShift Container Platform offers a range of hybrid cloud deployments, automated, on-demand scaling, and DevOps benefits. In addition, all agile integration components are API-driven, giving service providers flexibility to extend and integrate within an existing IT landscape.
Like all Red Hat offerings, Red Hat’s agile integration solution is based on open source community development. This model benefits from a large, global community of software developers who continuously contribute to and improve the code. In addition, Red Hat provides quality assurance, 24x7 support, and other benefits for transparency, security, speed, and innovation.
Red Hat has helped many CSPs worldwide, including managed service providers, implement APIcentric integration of internal and external systems. Benefits include compliance and security improvements, increased innovation, and reduced costs.
TABLE 1. REGIONAL RED HAT AGILE INTEGRATION USE CASES
NEXT STEPS WITH AGILE INTEGRATION
For communications service providers, effective integration of internal and external OSS and BSS systems and components is a technical, organizational, and financial challenge. Red Hat’s industryrecognized3 API-centric agile integration solution directly addresses service provider challenges with flexibility through distributed integration, scalability with containers, and reusability through managed APIs.
To initiate or expand API-centric agile integration, service providers can engage Red Hat Consulting in a Red Hat Discovery Session to analyze optimization potential for internal and third-party integration.
For a more comprehensive API-centric integration program, service providers can engage Red Hat for a Red Hat Consulting API-centric integration solution.
This solution includes and expands on a Discovery Session to help CSPs analyze requirements and establish best-practices for integrating internal, external, and partner systems.
It also identifies and translates business objectives into technology requirements and actionable items.
Learn more about other Red Hat offerings and expert services for communications service providers at redhat.com/telco.