X

Easy Access to WSO2's Online Resources During COVID-19 Lockdown.   Read More

Enterprise Integrator >

Product Roadmap

Updated 1H 2020

Near-Term

GRAPHICAL/CONFIGURATION-DRIVEN INTEGRATION
  • WSO2 Integration Studio and VS Code plugin for configuration-driven integration.
  • Micro Integrator—specializing in containerized deployments.
  • Native Kubernetes support.
  • Native CI/CD integration.
  • WSO2 Integration Studio Data Integration Tooling.
STREAMING INTEGRATION
  • For integration meditation on a stream of events, connecting different streaming sources and targets.
MICROSERVICES, CLOUD NATIVE OR MONOLITHIC
  • Natively support any architecture of your choice.

Medium-Term

CONNECTIVITY
  • EDI integration support.
OBSERVABILITY
  • Comprehensive logging, metrics, and tracing support for WSO2 EI runtimes.
ENTERPRISE MESSAGING
  • Native integration with NATS, Kafka, and ActiveMQ.
CDC AND ETL WITH STREAMING INTEGRATOR
  • Change Data Capture.
  • ETL with a stream processor.
DEVELOPER EXPERIENCE
  • Web-based tooling to augment Eclipse-based tooling.
  • Extending support for cloud-native ecosystems.

Future

SUPPORT FOR AD-HOC INTEGRATORS
  • Low code, graphical integration via WSO2 Integration Cloud.
COMPREHENSIVE HYBRID INTEGRATION PLATFORM
  • Integration in the cloud.
  • Control plane for integrations.
  • Kubernetes-native integration platform.
  • Graphical or configuration-driven hybrid integration in the cloud, on-prem, or hybrid.

Overview

Future integration needs in the application integration space should be able to meet microservices architecture and cloud-native needs.

When modernizing enterprise architecture, often, enterprises choose to incrementally migrate an SOA-based monolithic system by gradually replacing specific pieces of functionality with microservice architecture and implementing the new projects using a microservices architecture. WSO2 Enterprise Integrator will support this iterative, incremental move by supporting the best of both worlds.

When microservices are integrated, the proliferation of integration points is a key challenge to overcome. How would an enterprise deal with the number of microservices that result from transitioning to microservices architecture from an old-school, service-oriented architecture? What would be the demands and needs to address the vertical and horizontal split of service boundaries when it comes to integration? What would be the new requirements for message brokering, data decentralization, and cloud APIs? What about the requirements associated with cross-cutting concerns—such as security, traceability, and observability—in the new age of micro integrations? Micro-integration requirements, arising from cloud-native needs such as container readiness, fast boot ups, low footprints, a stateless nature, scalability, and short lives vs. long-running integration logic, are some of the requirements in the new integration age.

The composite apps resulting from integration would consist of consuming cloud APIs, cloud services, and internal and external services. These trends would also redefine security, CI/CD, DevOps, scaling, governance, observability, dealing with transactions, business process flow management, and message brokering. These will also necessitate many connectors that provide easy-to-use access to cloud APIs and services.

Vision

Our strategy for enterprise integration aims to offer solutions for layered and segmented architectural styles. We will facilitate these architectures to scale to thousands of integration points within an enterprise. Enterprises should be able to lifecycle-manage their integration solutions on cloud-native environments.

We will package our decade of experiences into our integration tooling, with seamless development, deployment, management, and administration tooling and techniques. We will also ensure that enterprise integration is secure, easy to test and debug, trace and monitor, scalable, agile, and future-proof. Support for security spanning from protocol-level security up to application-level security will be provided. IDE and command-line tools for development, deployment, and administration will be packaged with WSO2 Enterprise Integrator. Support for debugging and tracing will be packaged into tools.

As we continue to enhance and support our configuration-driven integrator runtime to cater to conventional enterprise integration needs, we will also evolve our enterprise integration strategy with WSO2 Integration Cloud to provide complete support for agile integration and API development. The solution will also facilitate iPaaS support for developing, deploying, executing, managing, and monitoring integration processes; APIs; and flows that connect multiple endpoints across cloud, on-premises, and hybrid deployments.

The key advantage for the integration developer is the ability to mix and match options for niche requirements, which an enterprise would have to realize a successful integration strategy; this will lead to a competitive advantage. We specialize in providing support for hybrid architecture, with centralized vs. decentralized integration for brownfield enterprises, combining cloud-resident and on-premises endpoints.

We also provide support for service mesh patterns, which ensures flexible, reliable, and fast communication between server instances. Enterprise Integrator will provide a clear separation of the data plane, control plane, and business logic to simplify the complexities involved with infrastructure and integration layer coordination. We will also provide built-in adaptive governance and surveillance capabilities to make the entire operation and management experience seamless.

Disclaimer

The content herein is shared in order to outline some of our current product plans but it is important to understand that it is being shared for INFORMATIONAL PURPOSES ONLY, and not as a binding commitment, promise or legal obligation to deliver any material, code or functionality. Any references to the development, release and timing of any products, features or functionality remains at the sole discretion of WSO2. Product capabilities, timeframes and features are subject to change.