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

Data Retention Options #107

Closed
andrewdodd opened this issue Oct 21, 2015 · 0 comments
Closed

Data Retention Options #107

andrewdodd opened this issue Oct 21, 2015 · 0 comments

Comments

@andrewdodd
Copy link
Contributor

New Feature Request
I think that the question of data retention is extremely important for users of this library. I also think that there are probably some pretty common problems that people will face and that there are only a few options available in the face of capacity problems. Thus, I think that this library should offer some basic retention options. (NB: The current batching feature is good for optimising performance, but cannot be used if you want to 'know' if your writes are successful).

In general, there are two classes of capacity limits:

  • Explicitly set limits (i.e. make my buffer N big please); and
  • Runtime limits (i.e. the system cannot supply the resources to meet the request).

In the face of these limits, I think there are a few possible responses:

  • Throw an exception
  • Block the thread until resources available (also could have an exception here)
  • Discard the current request
  • Discard the oldest buffered request.
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

2 participants