Hi Philipp, I think it's good to reduce the number of services - if more services with less pipeline elements are needed by anyone, they can always be built from source.
For the tutorial, we can integrate the vehicle simulator into a connect adapter and change the tutorial so that the first step is to create an adapter and reuse this in the pipeline editor afterwards. Dominik On 2022/06/02 15:09:01 Philipp Zehnder wrote: > Hi, > > we still had some old legacy files, from the time we had two separate > repositories. I deleted them. > > For development the following services are relevant: > > * backend > * ui > * all-extensions-jvm > * all-pipeline-elements-flink > Further I kept: > > * connect-adapters > * connect-adapters-iiot > * all-pipeline-elements-jvm > * sinks-internal-jvm > because sometimes they are helpful when only a reduced set of adapters, > processers, and sinks should be deployed. > > I also kept: > > * sources_vehicle_simulator_jvm > * sources_watertank_simulator > because we need them for the integrated tutorial. My suggestion would be to > change the tutorial, so we can also remove those as well. > > What do you think? > Any more ideas how we could further reduce the complexity of the > configuration and installation of the system? > > Cheers, > Philipp >
