| Table of Contents |
|---|
Information here will be moved to the Design Decisions Project Board once approved by the TSC
The EdgeX community has and will continue to explore issues of design and architecture of EdgeX Foundry, its many micro services, deployment mechanisms, testing apparatus, build process and more.
...
- How should concepts like Device or Addressable be uniquely identified? Currently using unique name strings
- How should persistent store identifiers be related/not related to these identifiers.
Closed Discussion Items
General
- Copyright header – stays the same (see contributor page) until LF has an alternative header and tool to provide
- Enums & JSON – use strings in place of any language specific enums or Iota in JSON messages and serialize/deserialize as necessary in your language of choice.
...
- How should micro services be identified uniquely and how should that relate to the address or host of the address?
- Proposed design doc on service naming, availability, configuration, etc.:
- ServiceNameDesign.odt
- ServiceNameDesign-v2.odt (inclusive of typos and clean ups and Trevor Conn comments)
- ServiceNameDesign-v3.odt (convergence of Tony/Trevor comments - keeping comments in areas still in need of cleanup/resolution)
- ServiceNameDesign-v4.odt
- ServiceNameDesign-v5.odt
- ServiceNameDesign-v6.pdf