trustification / trustify

Bringing together SBOMs and advisories.
Apache License 2.0
10 stars 20 forks source link

Finer grained processes #634

Open ctron opened 4 months ago

ctron commented 4 months ago

Today we have a single server binary trustd. However, I think we need an approach to a finer grained set of processes.

The main reason for that is that we might want to scale different functions independently. API services can be scaled independently. The importer server cannot, as that would lead to a concurrent run of the same importers as of today.

It would be ok to keep a single binary/container, but we would need to be able to select which features the command would provide. As a first step, it might be sufficient to just disable the importer server. On the other side, that would create a a special case just for that.

JimFuller-RedHat commented 2 months ago

This feels like we should consider once we have a k8s stage environment available or maybe we intend to dockerize and can start immediately - I am a bit torn eg. the simplicity of the current setup is great and any finer grain will come with complexity/infra/config costs. Alternately, maybe this is work done outside of trustify project.

helio-frota commented 2 months ago

the simplicity of the current setup is great and any finer grain will come with complexity/infra/config costs.

+1 this will probably make things more complex for konflux related tasks...

2024-09-19_09-38