Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [che-dev] Java extension is getting bigger

What exactly is the mechanics of the container merging? Is it something that plugin broker does? 
Do we expect the extension developers to explicitly mark their extensions for container merging?
--
Gorkem

On Mon, Nov 11, 2019 at 7:56 AM Gennady Azarenkov <gazarenk@xxxxxxxxxx> wrote:


On Mon, Nov 11, 2019 at 2:18 PM Thomas Mäder <tmader@xxxxxxxxxx> wrote:


On 11/11/2019 12:57, Gennady Azarenkov wrote:

Taking into account we are going toward real microservice architecture for IDE [1],
why we consider running several extensions in the same container as a target? 

"The version 7 of Eclipse Che introduces a new model of workspaces of workspaces where the IDE is splitted into multiple micro-services running in separate containers."

Our goal as an organization is not to provide an example of a microservices architecture. Our goal is to provide the best IDE for and on OpenShift/Kubernetes. If microservices are a good tool for that, fine, but an architecture is always a means, not a end.


Microservices are not "a tool" it is a way of providing the best IDE extensibility experience which is the main promise of Che 7.

I really do understand the complexity you face trying to solve this technical debt, but I doubt every time we face such a complexity a default way to solve is revising the project goals.
 

/Thomas

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev

Back to the top