...

• Improve/additional testing
  • Scale testing
  • Soak testing
  • Platform/OS Testing
  • Different configuration testing
• Automate generation of API documentation.  The RAML or Swagger/OpenAPI that provides developers with an understanding of the microservice REST calls is maintained by hand.  How can the generation and maintenance of the API documentation be more automated and therefore allow the documentation to be more reflective and consistent with the code base?
• Per Core WG of 10/14 - relook use of identifier in model/DTO; may allow name to be modified

No Longer Considered

• Allow for new category of micro services: “Sharing Services” for East/West data exchange with non-Edgex entities (too vague)

• Allow for device hierarchy in metadata model:  a device could be a manager for another device while also collecting data itself.  Sending a command to a managing device could mean sending a command to all associated devices. (too hard and not enough of a use case/demand to look at.  Different for each type of protocol)
• Better support mesh network protocols (Zigbee, BACNet, etc.) where devices know and sometimes manage other devices (see above)
• Command: in order to protect the device from harmful commands, there should be the possibility to set a Min and Max limit for the value that is accepted on every single command.  in fact the command service today is rather a hollow simple proxy, but in the future we very much envisioned adding additional security, caching to avoid having to hit the DS when unnecessary, and even grouping command requests for better resource conservation (especially for devices like BLE that get woken up when you hit them).  (This is more of a general security DoS type of attack to be explored universally at some point in the future)
• Support for alternate logging formats and/or more structured logging (logging service being deprecated in favor of using standard out and file system - which invites 3rd party tools to be used and any format supported by those tools)
  
  • XML, CSV vs JSON
• Integrate to edge software/agents (not enough demand or use case)
  • AWS Greengrass
  • Microsoft IoT Edge

• 0MQ export function (not enough demand or use case)

• Support additional northbound endpoints and protocol types.  (provide examples but not implement in services; like we do today for Azure, Amazon, etc.) Examples include:
  
  • Tencent
  • Alibaba
  • IBM Watson
  • IoTivity
  • SAP HANA
  • DDS
  • AMQP
• Educational Assistance (too vague)
  
  • Meetup support
  • Hackathon kits/support
  • Deeper documentation - especially around on-boarding
  • Provide more example code (Device Services, Application Services, etc.
• SDK alignment – can / should the DS and Application Functions SDKs be more aligned (design, usage, etc.)?  (To the extent possible, this is being looked at for filtering and some other functions.  Otherwise too vague and with no clear objectives)
• Implementation of message bus alternative for intercommunication between microservices as an alternative to REST.  (Being accomplished where there is a need.  Also have go-mod-messaging which makes it possible to institute where needed.)