Skip to content

Latest commit

 

History

History
24 lines (14 loc) · 1005 Bytes

0000-prefer-proven-foss-components-with-optional-support-for-licensed-derivatives.md

File metadata and controls

24 lines (14 loc) · 1005 Bytes
Raw

Prefer Proven FOSS Components with Optional Support for Licensed Derivatives

  • Status: accepted
  • Deciders: @k2merlinsix, @jam01
  • Date: 2020-08

Context and Problem Statement

Should we include licensed or non-FOSS components in the Tavros platform for a given component or component's feature?

Decision Drivers

  • Total cost of ownership
  • Providing the necessary features for a competitive product

Decision Outcome

We will prioritize FOSS components, while providing optional support for paid or licensed derivatives, e.g.: Elastic Stack Open Source vs Enterprise subscription, Apache Camel vs JBoss Fuse, etc.

Ultimately total cost of ownership will be the deciding factor for our customers when comparing to established alternatives. There are many FOSS components that address different concerns that we can incorporate and still provide a best-in-class platform.

Negative Consequences

  • High number of components to configure and integrate