search

wso2 / product-ei

An open source, a high-performance hybrid integration platform that allows developers quick integration with any application, data, or system.
https://wso2.com/integration/
Apache License 2.0
373 stars 280 forks source link

WSO2 EI 6 vs WSO2 EI 7 #4940

Open scholtz opened 4 years ago

scholtz commented 4 years ago

Description: Hi, I am trying to understand update to WSO7 product line. On the site you promote wso7 as something that is latest, however I am not able to understand why in product-ei in the tags 7.* there is no stable release, nor why the latest update was more than 2 years back, and v6.6 was released quite recently

Also I am not able to see any dashboard in wso7 branch, so technically it is probably totally different product? Why do you promote wso7 as enterprise integrator when there are only 3 parts - balerina integrator, micro integrator and streaming Integrator. Where is graphical editor of DSS? Is the proposed way to install integration studio on the computer of some administrators so that they manages some process flow or what do you think is the best practicies of your usage?

I have fixed some broken links on your readme file here on git #4939 but for me it seems that you are focusing on developing v 6.*

Am I missing something?

Suggested Labels: wso-ei-6, wso-ei-7

Suggested Assignees:

Affected Product Version: none

OS, DB, other environment details and versions:
i deploy wso-ei-6 instances to k8s through docker images, but i am not able to find correct subsidiaries for wso-ei-7

Steps to reproduce:

Related Issues:

arunans23 commented 4 years ago

Description: Hi, I am trying to understand update to WSO7 product line. On the site you promote wso7 as something that is latest, however I am not able to understand why in product-ei in the tags 7.* there is no stable release, nor why the latest update was more than 2 years back, and v6.6 was released quite recently

Micro Integrator which comes with EI 7 does not originate in the product-ei repository but maintained in a seperate repository. (https://github.com/wso2/micro-integrator)

Also I am not able to see any dashboard in wso7 branch, so technically it is probably totally different product? Why do you promote wso7 as enterprise integrator when there are only 3 parts - balerina integrator, micro integrator and streaming Integrator. Where is graphical editor of DSS? Is the proposed way to install integration studio on the computer of some administrators so that they manages some process flow or what do you think is the best practices of your usage?

EI 7 does not have a management console, but rather have a monitoring dashboard to monitor the CAR files that are deployed. For all the development purposes, you need to use the Integration Studio which is used to create the CAR files.

EI 7.0 is the next generation of WSO2 Integration platform and mainly focuses on micro-service architecture and cloud-native architecture. This integration platform mainly offers a code-driven approach to integration development. Kindly note that the development of EI 6.x series is still being continued. We maintain the EI 6xx series for those who are familiar with existing Enterprise Integrator. We released EI 6.6 recently with JDK 11 support and many other features. For more details you can refer the documentation here. https://ei.docs.wso2.com/en/latest/micro-integrator/references/comparisong-mi7-ei6xx/

To see the evolution of Micro Integrator (Integration runtime of EI 7 series), please visit https://medium.com/think-integration/life-of-mi-how-an-esb-went-on-to-serve-microservices-9bb4faed5588

OS, DB, other environment details and versions: i deploy wso-ei-6 instances to k8s through docker images, but i am not able to find correct subsidiaries for wso-ei-7

For the ESB profile, you may need to find Micro Integrator related docker files. https://docker.wso2.com/tags.php?repo=wso2mi

scholtz commented 4 years ago

hi @arunans23 , thanks for your feedback

my organization wants to start new project, and we consider wso as the gateway service

we would like to use the kubernetes, and use the visual studio and .net core for the development of some specific services

there is some experience in the company using the wso ei 6.x, and the guys got familiar with the DSS, and proxying of services

from your answer (and some other research) I assume

  1. DSS is no longer to be supported, only in the form of balerina definition of datasources
  2. without integration studio we cannot deploy services to dev/test/stage/prod
  3. In 6.x version, we could for example in k8s set the configmap file to some directory and configure this way the wsoei/wsois. in 7+ version this is not possible

Is this correct?

arunans23 commented 4 years ago

@scholtz Please see my inline replies.

hi @arunans23 , thanks for your feedback

my organization wants to start new project, and we consider wso as the gateway service

we would like to use the kubernetes, and use the visual studio and .net core for the development of some specific services

there is some experience in the company using the wso ei 6.x, and the guys got familiar with the DSS, and proxying of services

from your answer (and some other research) I assume

  1. DSS is no longer to be supported, only in the form of balerina definition of datasources

DSS is still supported in EI 7 series. However, the developer experience might differ from EI 6xx to EI 7 since the management console is not available in EI 7. All the DSS related development activities should be done through Integration Studio. (Please also note that we have done a major revamp of our Integration Studio DSS developer experience. We will release an update to the Integration Studio very soon). Also please note the below point regarding Ballerina Integrator on our recent strategic announcement.

To provide a more focused enterprise integration experience to our customers and community, WSO2 has made a strategic decision on the composition of the WSO2 Enterprise Integrator 7 product suite. Ballerina Integrator, which is based on the Ballerina programming language, will no longer be a part of the WSO2 Enterprise Integrator.

  1. without integration studio we cannot deploy services to dev/test/stage/prod

Integration Studio is used to create the services and pack them inside CAR files. How you choose to deploy the CAR files is totally up to you. Addition to that Integration Studio provides the feature of creating Docker and K8s resources. You don't have to depend on Integration Studio to deploy them in dev/test/stage/prod environments.

  1. In 6.x version, we could for example in k8s set the configmap file to some directory and configure this way the wsoei/wsois. in 7+ version this is not possible

In EI 7, we introduced a new configuration model and we maintain only one file to store configurations. Even though the conf folder exists in EI 7 (similar to EI 6xx), the changes you do in those files will be overridden by the deployment.toml file in server startup. Maintaining one file will be more comfortable and easy in container world. You can use the following link to read more on deployment.toml file. https://ei.docs.wso2.com/en/latest/micro-integrator/references/config-catalog/

Is this correct?

What I would like to point out is, even though the developer experience would have changed from EI 6xx to EI 7, most of the functionalities still remain the same. The need to change to this model arised due to the need of Developers moving towards Micro services architecture and Container world. If you have any more queries you can also join our slack channel. https://ei-slack.wso2.com/