For the latest iteration of its enterprise application and data integration platform, WSO2 has created petite versions of all its components that can run smoothly in a microservices environment.
Along with the WSO2 Integration Agile Platform, users have the option of running pared-down and microservices-tuned containerized versions of the software’s API gateway, enterprise service bus, identity server and stream processor. By slimming these components, they can boot up much more rapidly, within a few seconds, rather than the 40 second boot time typically required for the full versions.
The company announced these new features at the company’s WSO2Con user conference, being held this week in San Francisco.
WSO2’s enterprise service bus (ESB), which is software that facilitates communications between multiple endpoints, has all the features that would be required to coordinate a microservices-based system. “The one problem we had had putting it in microservices environment was start-up time,” explained Isuru Udana, WSo2 senior technical lead.
Unlike, say, an enterprise Java environment run under an ESB, container-based microservices are always being set up, shut-down and moved around depending on the amount of work the system is getting.
Integration is hot again — @Gartner_inc says half of all the work and costs for digital platform development projects will go into data and app integration— @TylerJewell #WSO2Con @wso2 #sponsored pic.twitter.com/VrkIYvk74z
— The New Stack (@thenewstack) July 16, 2018
With this faster bootup, the software can keep pace with the dynamic nature of the microservices environment. These components can then be attached to microservices as sidecars, allowing the organization to set up a fully defined microservices system with these components handling the messaging, identity management and other common functionality.
The specific components offered in a slim-down form factor are:
- API Microgateway can “serve as a dedicated proxy for a microservice, a sidecar for a microservice running on the same host, or an API hub that proxies one or more microservices,” according to WSO2 promotional material.
- Stream Processor, for analytics, is “a lightweight runtime that can run in distributed deployments using Kafka and container-native environments, such as Kubernetes.”It offers message tracing across microservices using the OpenTracing standard.
- MicroESB, a lightweight mediation runtime that includes all core mediation capabilities.
- Identity Server manages user identities, global authorization policies, and acting as a trust broker for user identities across enterprise-level trust boundaries.
In order to pare down the ESB software, WSO2 removed some of the features not typically required for microservices work such as support for multitenancy environments, where multiple isolated namespaces are created. But the core features of the ESB remain intact for the micro edition, such as transformation, orchestration, protocol switching and routing, Udana explained.
In a microservices setup, each microservice would get, as a sidecar container its own ESB and other required components, and that microservice would speak only with that sidecar. Although this approach will probably vary from set-up to set-up, in general, this approach would be a decentralized architecture, with the business logic encapsulated in the MicroESBs.
WSO2 is a sponsor of The New Stack.
Feature image: For the kickoff of WSO2Con, WSO2 hired Brazilian drum dancers to show how sexy integration has gotten again.