WSO2 Micro Integrator vs WSO2 EI 6.x Family¶
Comparison: EI 6.x vs EI 7.0¶
WSO2 Enterprise Integrator consists of two product families:
- WSO2 EI 7.x.x family
- WSO2 EI 6.x.x family
WSO2 EI 6.5.0 is the latest release of the 6.x family, which includes the ESB profile and other supporting profiles. This WSO2 EI product family offers the conventional, centralized integration solution of the WSO2 middleware stack. The next release of the 6.x family would be EI 6.6.0 that includes support for JDK11.
The new WSO2 Enterprise Integrator (WSO2 EI 7.0.0) is a hybrid platform that enables API-centric integration supporting various integration architecture styles: MSAs, cloud-native architecture, or a centralized ESB architecture. This integration platform offers the choice between code-driven and graphical/configuration-driven approaches to integration development.
The following are the three approaches to integration with EI 7.0.0.
Code-driven Integration with Ballerina Integrator
The Ballerina Integrator provides a powerful, simple-to-learn, code-driven approach to programming integration solutions based on the Ballerina programming language. The Ballerina language offers a revolutionary approach to closing the integration gaps often left by traditional ESBs when supporting modern, cloud-native app development. The Ballerina Integrator simplifies integration by offering high-level abstractions that represent services, endpoints, and network data types, along with a sequence diagram-based visualization of interactions.
Low-code Integration with Micro Integrator
The Micro Integrator is an intuitive, configuration-driven integrator with graphical/drag-and-drop integration designing based on the cloud-native variant of the battle-tested WSO2 EI/ESB runtime.
The Streaming Integrator is a cloud-native, lightweight component that understands, captures, analyzes, processes, and acts upon streaming data and events in real-time. It utilizes the SQL-like query language ‘Siddhi’ to implement the solution.
As explained above, EI 7.0.0 addresses a wider audience that prefers different approaches to integration.
Advantages of using the Micro Integrator in EI 7.0¶
Compared to the ESB profile of WSO2 Enterprise Integrator 6.x, the Micro Integrator encompasses the following key attributes that are essential for a microservice-ready integration solution.
- Faster startup time (<3s).
- Low memory footprint.
- Stateless services.
- Immutable services.
- Native Kubernetes support with the integration operator.
- Lightweight, container-native, and supports distributed deployments.
Comparison: ESB profile of EI 6.x vs Micro Integrator of EI 7.0¶
Given below is a comparision between the Micro Integrator of EI 7.0 and the ESB profile of EI 6.x.
|ESB Profile||Micro Integrator|
|Distribution Size||~600 MB||~100 MB|
|Product configuration model||XML-based configurations||TOML-based configurations|
|Mediation (ESB) Features||Available||Available|
|Data Integration Features||Available||Available|
|Clustering||Built-in||Using container orchestration|
|Tooling||WSO2 Integration Studio||WSO2 Integration Studio|
|Runtime monitoring and management||Managemement Console||Micro Integrator Dashboard Micro Integrator CLI|
|Registry||RDBMS-based Registry||File system based Registry|
|Artifact deployment||Hot deployable, Hot updatable||Immutable artifacts|
Features removed from the Micro Integrator of EI 7.0¶
The following features, which are not needed for MSA-based deployments or not used frequently are removed from WSO2 Micro Integrator.
|Management Console||WSO2 Integration Studio is the recommended tool for developing integration solutions. The monitoring capabilities available in the management console (of the ESB profile) are available through the new Micro Integrator dashboard.||Micro Integrator Dashboard|
|Multitenancy||This is not a widely used feature in the ESB profile. Multitenancy does not suit the world of microservices or micro integrations.||-|
|Svn based Dep-sync||This is not a widely used feature in the ESB profile, and is not recommended for use.||Third-party offering like rsync|
|Hot deployment/Hot update||Services and artifacts are immutable.||-|
|Built-in Hazelcast-based clustering||The microservices world typically handles clustering using a container orchestration systems like Kubernetes.However, built-in clustering support will be added to the Micro Intgrator in a future version to support standard, centralized deployment architectures.||-|
|Built-in node coordination feature||Coordination support for message processors, inbound endpoints, and tasks, which is built into the ESB profile, is removed from the Micro Integrator. This feature is not a requirement in the microservices world. However, coordination support will be added to the Micro Integrator in a future version to support standard, centralized deployment architectures.||-|
|Database-based Registry||-||File system based Registry|