| Re: [kapua-dev] Making device registry available as a standalone microservice |
[2] https://github.com/Hi,
Several people in a community seem to be interested in running Kapua in a microservice oriented fashion. Device registry is probably the first thing that comes to mind for microservices architecture and Kapua. I think it is reasonably low hanging fruit to provide a way to run device registry as a self-contained service in Docker/Kubernetes environment.
I would like to provide a support for standalone device registry microservice with pluggable transport support, so you could access it using MQTT, AMQP or REST.
I would like to create a dedicated
kapua-device-module (here [1]) containing bootstrap code for device registry and initial version of a transport binding logic (which we can later extract to a common module to share it among other Kapua microservices).registry-standalone What do you think?
I have also created a GitHub issue [2] to track discussion and development related to this effort.
Cheers!
[1] https://github.com/
eclipse/kapua/tree/develop/ service/device/registry eclipse/kapua/issues/497 --Henryk Konsek
_______________________________________________
kapua-dev mailing list
kapua-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kapua-dev