This repository has been archived by the owner on Apr 22, 2020. It is now read-only.

Make reporting to data-service more resilient #277

Open

mohabusama opened this issue Oct 17, 2017 · 0 comments

Labels

feature investigate Revisit

Contributor

mohabusama commented Oct 17, 2017

As data-service could get throttled by downstream components, we may try to better handle reporting back data:

Initial thoughts:

Ensure failure is handled properly (e.g. 5xx vs 4xx?)
Implement circuit breakers
Use Redis as temp data storage during backoff
Compress data storage (e.g snappy)

mohabusama added feature investigate labels

beverage added question Revisit and removed question labels

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.