search

it-at-m / digiwf-project

Project repo for the DigiWF project automation platform.
MIT License
10 stars 1 forks source link

[feature] Concept to create own integration artifacts & services #34

Closed xdoo closed 1 year ago

xdoo commented 2 years ago

Is your feature request related to a problem? Please describe. A less experienced (in DigiWF context) user should be able to create fast a new integration artifact or other microservice. All necessary functionality should be provided in a easy to use manner.

Describe the solution you'd like

Implement a set of Spring-Boot-Starters to enable developers to craft their own customized integration artifacts in no time.

Integrationskonzept für Services _ Feature Requests _ Ablaufdatum S3 (4)

Describe alternatives you've considered Everybody codes everything on his own.

xdoo commented 2 years ago

@dominikhorn93 @boal

dominikhorn93 commented 2 years ago

@xdoo I think it makes sense to separte the different APIs in different starters (xxx-starter-rest, xxx-starter-event) In my opinion, however, we don't need an event-producer or consumer base starter. We have already abstracted that via Spring Cloud Stream.

xdoo commented 2 years ago

@dominikhorn93 this ticket is not about tailoring starters. The picture is only an example to show my thoughts. I want a bunch of suitable (the definition of suitable is up to the dev) bricks, that a less experienced user can put together to a running service in no time.

I want something like that :joy::

image

darenegade commented 1 year ago

@dominikhorn93 Isn't this about documentation? How do we cut integrations (Core vs. Starter vs. Service) and how are the starters used?

In my opinion, one can already create integrations relatively quickly (Oce-Cosmos), but you have to know how to start.

Maybe we have to refactore some of the integrations to meet that agreement.

darenegade commented 1 year ago

Documentation was created within this PR : https://github.com/it-at-m/digiwf-core/pull/173