- Revolutionized way for integration with Ballerina programming language which is designed for building and integrating network distributed applications.
- WSO2 Integration studio and VS Code plugin for configuration driven integration.
- Micro Integrator specializing containerized deployments.
- Native Kubernetes support.
- Native CI/CD Integration.
- Using Siddhi.io for integration meditation on stream of events, connecting different streams sources and targets.
Microservices, cloud native or monolithic
- Natively support any architecture of your choice.
- Strengthening integration capabilities of Ballerina Integrator (SaaS, proprietary connectors)
- EDI Integration support
- Comprehensive logging, metrics and tracing support for WSO2 EI runtimes.
- Native integration with NATS, Kafka and ActiveMQ.
CDC and ETL with Streaming Integrator
- Change Data Capture
- ETL with stream processor
- Web-based tooling to augment Eclipse-based tooling
- Extending support for Cloud Native ecosystem
Support for Ad-hoc Integrators
- Low code, graphical integration based on Ballerina Integrator runtime.
Comprehensive Hybrid Integration Platform
- Integration in the cloud
- Control plane for integrations
- Kubernetes native integration platform
- Code, graphical or configuration driven hybrid integration in the cloud, on-prem or hybrid
The Integration needs in the future application integration space would need to be able to meet the microservices architecture and cloud-native needs.
When modernizing the 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 microservices architecture. WSO2 Enterprise Integrator will support this iterative incremental move by supporting best of both worlds.
When microservices are integrated, the proliferation of integration points would be a key challenge. How would an enterprise deal with the number of microservices that result from old-school service-oriented to microservices 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? The micro integrator requirements arising from cloud-native needs such as container readiness, fast boot, low footprint, stateless nature, scalability, 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, internal and external services. These trends would also redefine security needed, 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.
Our strategy for enterprise integration would be to offer solutions to all architectural styles including layered, segmented and cell-based. We will facilitate these architectures to be able to scale to thousands of integration points within an enterprise. Enterprises would 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 the 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 the enterprise integrator. Support for debugging and tracing will be packaged into tools. Streaming analytics with customizable dashboards for detailed monitoring will be provided with the analytics profile.
As we continue to enhance and support our existing configuration driven integrator runtime to cater for conventional enterprise integration needs, we will also evolve our enterprise integration strategy to support agile integrations with microservices and cell-based architecture implemented using code over config development model. Integration agile architecture and methodology will benefit from the native cell-based architecture support provided by WSO2 Enterprise Integrator. This will make the integration developer’s life simple in harmony with the agile application integration, deployment and lifecycle management aspirations of the organization.
iPaaS support for developing, deploying, executing, managing and monitoring integration processes and flows that connect multiple endpoints across cloud, on-premises and hybrid deployment would be facilitated. The key advantage we provide for the integration developer is the ability to mix and match the choices of deployments for catering niche requirements that each enterprise would have in realizing a successful integration strategy that would lead to 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.
Support for service mesh patterns that 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 make the whole operation and management experience seamless.
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.