Hi guys,

This is a follow up VOTE spawn by the discussion (same subject)

Most of you are aware that the configuration supported by the project
(the compact architecture) only is supported by quarkus and not SB.
This might impact the project adoption in one of the most used
microservice frameworks (or standard de facto) for building
microservice.

The one thing stopping us from supporting this runtime in compact
architecture is these components that require some attention.

We already have patterns on how to deal with this sort of problem.
(multiple runtime support), so ideally is to use them to upgrade these
components to use those and add support for the runtime. Basically
would be

1. identify the common components and isolate properly without any runtime use.
2. minimize the codebase deployed in runtime (should be a thin layer)
3. Move the generic tests to the common components and integration
tests to the runtimes components)
4. remove all features that are not shared among runtimes or they are
incompatible among runtimes to avoid code duplication and therefore
reduce the sustaining effort.
5. common runtime code to its own code module


Please state VOTE and if you have a preference to take care any of
these components
Job Service
Data Index

(keep in mind that this requires commitment as this is intended to be for june.

Cheers :)

-- 
Saludos, Enrique González Martínez :)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org
For additional commands, e-mail: dev-h...@kie.apache.org

Reply via email to