https://wiki.edgexfoundry.org/pages/resumedraft.action?draftId=27492626&draftShareId=db95aed1-c8f9-4325-a544-f4727e377e22&src=shareui&src.shareui.timestamp=1554131234379

https://github.com/edgexfoundry/device-bluetooth/blob/master/deviceprofile_samples/TI_CC2650_profile.yml

+2

+1

DeviceResourcesDeviceCommandsCoreCommands

+1

https://docs.google.com/document/d/1OdEEU2q82jJ3NIWdQF6QdYN6Qwfe-e6TAOIP7u_Fxwc/edit#heading=h.jyuvcu11vi9d

For device services, service keys are hard coded. Example:https://github.com/edgexfoundry/device-mqtt-go/blob/c396927824ca74965b37c9f118ae08711a9b3582/cmd/main.go#L17

When the registry is in-use, the original idea was that the [service] registry would provide the functionality to prevent multiple instances of a service from being started via it's registration mechanism. This is one of the reasons services should unregister themselves on graceful shutdown. That said, I'm not sure how we handle this if a service crashes.

Java frameworks have solved this a long time ago

Can somebody help with the notes for this conversation?

We need 12 factor for all services before that

Have to leave for my next call - thanks everyone. Good discussions.

Gotta drop. Thanks.