Skip to content
This repository has been archived by the owner on Aug 21, 2021. It is now read-only.

Use Websockets for Monitoring Services #8

Closed
AusIV opened this issue Oct 16, 2017 · 1 comment
Closed

Use Websockets for Monitoring Services #8

AusIV opened this issue Oct 16, 2017 · 1 comment

Comments

@AusIV
Copy link
Contributor

AusIV commented Oct 16, 2017

The current monitoring services (the exchange fill monitor and the block monitor) use HTTP polling to monitor for changes. This means:

  • We have extra traffic going back and forth between services
  • We can't trivially load-balance the monitoring services, because they need to talk to the same backend consistently.

Geth supports a websockets subscription endpoint that can provide the same information over a websockets connection, which would have less back-and-forth traffic, and would mean we could establish a connection with any available Ethereum node and it would be good for the life of the connection.

@AusIV
Copy link
Contributor Author

AusIV commented Jun 1, 2018

This has been superceded by the new monitoring system we've put in place.

@AusIV AusIV closed this as completed Jun 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant