search

eclipse / eavp

Eclipse advanced visualization project
Eclipse Public License 1.0
9 stars 15 forks source link

Migrate from RCP to microservices #176

Open MarkAMartin opened 5 years ago

jayjaybillings commented 5 years ago

1) Remove RCP files where possible, including plugin.xml, etc. However, watch out for cases where MANIFEST.mf is required. 2) Move to regular Maven instead of using an Eclipse Target and Tycho. 3) Where possible, err on the side of caution with service side by making sure that each service only does one thing. This could entail breaking up the viz.service package, for example, into a registration service and viz services. Note that interface definitions such as IVizService etc. would exist in their own bundle as a dependency that may be shared across services.

jayjaybillings commented 5 years ago

The reason we want to go to microservices to begin with is that we have decided to move EAVP to the web. Since EAVP is already a service-based platform with multiple services that do only one thing, a web-based microservice architecture appears to be a natural extension of this decision to move to the web.

Note that we are being a little more rigorous in our definition of a microservice and our implementation of the services in EAVP. We will have a certain amount of homogeneity across the services since we are using Java and RESTful services (maybe JAX-RS?) with Spring Boot, versus more stereotypical microservice architectures that allow anything and everything to join up.

MarkAMartin commented 5 years ago

Let's ensure we have unit tests for this block of work (and the other associated tickets). Also, let's explore CI/CD for this. Happy to discuss those points at the appropriate time.

SmithRWORNL commented 5 years ago

The microservice version is now in Robert/MicroServices as of commit a88ad3826596dc80cf6291b617f567f4c4eac039