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

Plan for Meetup Outages #33

Open
rdohms opened this issue Dec 5, 2013 · 3 comments
Open

Plan for Meetup Outages #33

rdohms opened this issue Dec 5, 2013 · 3 comments

Comments

@rdohms
Copy link
Member

rdohms commented Dec 5, 2013

Currently the site uses short term caches for all api calls.

However if the API throttles us or bugs out the site pretty much crashes, this should be improved and it should be more resilient to these failures.

@pascaldevink
Copy link
Member

You mean like a introducing a circuit breaker pattern with a fallback? Or just plain try/catch with a nicer error message?

@rdohms
Copy link
Member Author

rdohms commented Oct 8, 2014

Ideally something more long term without so much error messages, but given how little issues we have had, this may not be as important anymore.

@pascaldevink
Copy link
Member

A small circuit breaker can be nice to introduce to the meetup bundle. This doesn't necessarily be a big thing, but enough to be done by a person on the hackathon for example. Specially for someone who's interested in the more backend jobs, this is a nice example.

It could be as simple as including and using Arthur Esjmont's bundle: https://github.com/ejsmont-artur/php-circuit-breaker-bundle or whip up something of our own, following his writeup: http://artur.ejsmont.org/blog/PHP-Circuit-Breaker-initial-Zend-Framework-proposal

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

3 participants