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

Add support for Marathon's Event Stream API #52

Open
JayH5 opened this issue Jan 20, 2016 · 0 comments
Open

Add support for Marathon's Event Stream API #52

JayH5 opened this issue Jan 20, 2016 · 0 comments

Comments

@JayH5
Copy link
Contributor

JayH5 commented Jan 20, 2016

At the moment we use the Event Subscription API which requires that Consular runs an HTTP server to listen for requests from Marathon. Since Marathon 0.9.0, the Event Stream API has provided a way to receive events using Server Sent Events which does not require an HTTP server.

There is nothing technically wrong with the way we are doing things now, it's just that using the event stream has some advantages:

  • Don't need to run a server on a certain interface/port
  • Fewer config parameters necessary
  • Simplifies things if we ever run Consular in a Marathon-deployed container as we don't need to worry about dynamic ports/addresses
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant