The following figure provides some hints to understand how to give value to your first work on EDITO, by contributing either to the service layer, the process layer or the data layer.

Once you start to contribute to each layer independently, you are encouraged to exploit all EDITO layers to architect your contribution.

Both service and processes types run on internal EDITO computing cluster. However, using containers, they can rely on external resources (data, storage, computational resources) that should be hidden to end-user for simplicity. Moreover, enabling seamless direct run on external infrastructures is foreseen and currently evaluated.

The separation between services and processes is there for both your architectural need and for the reusability of your work.

For example, you could build an end-user application that launches your underlying processes with specific inputs, and then allows the end-user to explore the output data within the application.

Moreover, nothing prevents one process to launch others sub-processes in background.

In addition, be aware that you can “hide” several containers under a single service (hence, a single tile in the catalogue UI). In doing so, end-users have a single point of entry to launch and access your service even if, under the hood, your service relies on a database for example.

Finally, you can also take advantage of the tutorial engine to create and host description/documentation pages, and to provide a “Launch” button to directly launch your service with a particular configuration.

The service and process deployments rely on contribution tools and helm chart repositories versioned using Gitlab. To get write access to public contributing repositories on Mercator Ocean Gitlab instance please contact the support using the widget in the bottom right corner.

Check-out the following tutorials:

If you have any questions, problems, or suggestions, please feel free to contact us via chat using the widget available at the bottom right of the page.