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

Make the hit counter persistently survive service restarts #4

Open
rofrano opened this issue Sep 21, 2016 · 0 comments
Open

Make the hit counter persistently survive service restarts #4

rofrano opened this issue Sep 21, 2016 · 0 comments

Comments

@rofrano
Copy link
Collaborator

rofrano commented Sep 21, 2016

As a User
I need the hit counter to persist the last known count
So that I don't loose track of the count after the service is restarted

Assumptions

  • We will use Redis as the persistent store
  • A Redis service from Bluemix should be used

Acceptance Criteria

Given the hit counter is at 1
When I advance the hit counter to 2
And I restart the hit counter services
And I call the hit counter URL
Then I should see 3 returned from the service
@rofrano rofrano added this to the Sprint 1 milestone Jan 31, 2017
@rofrano rofrano removed this from the Sprint 1 milestone Feb 8, 2017
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