You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 11, 2021. It is now read-only.
tadaskay
changed the title
Should we use DNS or service discovery (zookeeper, etc.) for resolving featuros dashboard?
Should we use DNS or service discovery?
Jun 30, 2015
Do you mean 'how should featuros-plugin locate the back-end it reports to'?
I feel the need for a versions dashboard has its source - to some extent - in lack of zookeper integration for most of our apps. At least this was one of the things that made me think about such a dashboard.
I think that not being able to use the dashboard with apps not using zookeper would be a serious drawback. That's why I'd suggest first locating the dashboard via dns and later on resolving it using zookeeper.
Also, I think zookeeper could be of use itself: I think for a zookeeper-registered app we could get some of the information featuros-plugin intends to provide without even having the plugin in the app. Or, at least, we could detect apps that still need to be assimilated.
EDIT: please note I might have misunderstood some of the ideas behind the project. So, correct me if I'm wrong :)
For locating featuros backend (dashboard) we could use DNS or service discovery (zookeeper, etc.). Or we can do both.
Discuss!
The text was updated successfully, but these errors were encountered: