Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unecessary discovery layer #2

Closed
claustres opened this issue Sep 8, 2017 · 1 comment
Closed

Unecessary discovery layer #2

claustres opened this issue Sep 8, 2017 · 1 comment

Comments

@claustres
Copy link
Member

cote already gives us service discovery out of the box so we don’t really need to publish any service definitions ourselves. The only thing we need is to create corresponding service level requesters/publishers and responders/subscribers. Then a requester will discover all the other responders, a subscriber will discover all the other publishers (and vice versa).

A monitor that discovers everything regardless of environments could also be used.

@claustres
Copy link
Member Author

I am not sure this would be possible because cote is initialized early in the app lifecycle, so that some events can be received while the app is not really ready to process them.

It seems safer to have our own layer where we can control the event flow, closing for now.

claustres added a commit that referenced this issue Oct 21, 2019
Changed the way default options are managed
#2 (comment)) and added key to improve performances
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant