policy approved by the TSC September 14, 2020
EdgeX uses many open source infrastructure elements to deliver the platform. This includes, but is not limited to databases, messaging systems, registry subsystems, security capability and more. Traditionally, the TSC has voted on the inclusion and upgrade of all infrastructure elements. Even including a patch release of an infrastructure element required the TSC consent.
Going forward, infrastructure will now be under the purview and decision making authority of the assigned working group (and working group chair initiative). A working group can make the decision as to what and when infrastructure is needed for their delivery area. The working group chair will keep the TSC informed of all infrastructure changes (via the TSC chairperson). The table below specifies what infrastructure is currently included in EdgeX and now under the control of the associated chairperson. This list should be updated with new infrastructure as it is included in the project.
|Infrastructure element||Working Group Control||Notes/consideration|
|API Gateway||Security Working Group||Currently Kong|
|Secret Store||Security Working Group||Currently Vault|
|Service Registry/Configuration provider||Core Working Group||Currently Consul; considered a cross cutting concern|
|Database||Core Working Group||Currently Redis; considered a cross cutting concern|