...
- Implementation of message bus alternative for intercommunication between microservices as an alternative to REST (REST won't go away, but alternative to be provided for asynchronous and better QoS needs).
While REST will not go away (a REST API will still exist around each micro service), there may be a need to implement point-to-point messaging between select services or to adopt some type of message bus unilaterally across all of EdgeX to support messaging among services.
Messaging provides for more asynchronous communications, typically lower latency communications, and better (or more finely tuned) communication quality of service (QoS). Are there places where messaging might be more appropriate (like between core data and export distro today). Would a use case dictate the use of an alternate messaging infrastructure be used among all services with an underlying message bus to support it? Would alternate protocols (SNMP, WebSockets, etc.) be desired in some use cases? For the Delhi release, some alternate communication requirements, design and early message implementation experimentation is likely to occur.
- Improved performance to continually lower footprint, data collection and actuation latency, lower startup time, etc. which began with the California Release
- Implementation of additional priority features for security and manageability
- Potentially, implementation of specific services and SDKs in C to support deterministic real time use cases (see section below for more details)
- Certification process for EdgeX-compliant microservices to enable a plug-and-play ecosystem
- Validate Various levels of certification are being considered, from micro service replacement certification (validating alternate or commercial implementations of EdgeX (full platform or discrete microservice) satisfies key APIs and deployment/delivery facilitiesmicro services satisfy API requirements along with performance metrics and quality checks) to full EdgeX deployments (for commercial versions of EdgeX)
- Additional certification processes may be developed around particular cross cutting features such as security.…
- Facilitate East/West capability
- Microservice load balancing, failover, scale-over, ...
- Device from EdgeX A triggers action on device on EdgeX B
- Address data privacy concerns
- EU laws and affirmation about data use/storage/etc.
- HIP-A
...
- California release was focused on initially securing the EdgeX “gateway” and remains the priority
- This work will be extended / augmented in this release (looking at alternative authentication, adding MQTT and other protocol reverse proxy, etc.)
- This work will be extended / augmented in this release (looking at alternative authentication, adding MQTT and other protocol reverse proxy, etc.)
- Code signing – how to certify integrity of the system
- The release will start to explore, potentially, securing EdgeX’s devices
Explore potential use of hyperledger
...