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.

Sign up for GitHub

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

Jump to bottom

IMPORTANT: we need a distributed/replicated cache/event system for blog content #97

Closed
jlchereau opened this issue Apr 11, 2016 · 1 comment
Closed

IMPORTANT: we need a distributed/replicated cache/event system for blog content #97

jlchereau opened this issue Apr 11, 2016 · 1 comment
Labels
discussion enhancement wontfix
Milestone
v0.3.0

Comments

@jlchereau
Copy link
Member

jlchereau commented Apr 11, 2016 •
edited
Loading

Replicated/Distributed Cache (cache is shared between nodeJS instances):

Distributed Events (each instance has its own cache, but receives an event from the webhook instance triggered) :
@jlchereau jlchereau added this to the vNEXT milestone Apr 11, 2016
@jlchereau
Copy link
Member Author

jlchereau commented Apr 12, 2016 •
edited
Loading

Might be a bit complicated. Simply refresh the cache with the source every T time span (period).

So now refer to #98

@jlchereau jlchereau modified the milestones: vNEXT, v0.3.0 Sep 16, 2016
@jlchereau jlchereau mentioned this issue Sep 24, 2016
Open
@jlchereau jlchereau changed the title IMPORTANT: we need a distributed/replicated cache for blog content IMPORTANT: we need a distributed/replicated cache/event system for blog content Sep 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion enhancement wontfix
Projects
None yet
Milestone
v0.3.0
Development

No branches or pull requests
1 participant
@jlchereau