5 Things I Have Learned Using Celery And Social Networks For Disaster Relief
•
4 gostaram•1,665 visualizações
EuroPython 2013
Recomendados
Mais conteúdo relacionado
Semelhante a 5 Things I Have Learned Using Celery And Social Networks For Disaster Relief
Semelhante a 5 Things I Have Learned Using Celery And Social Networks For Disaster Relief (20)
Mais de Andrew Mleczko
Mais de Andrew Mleczko (10)
Último
Último (20)
5 Things I Have Learned Using Celery And Social Networks For Disaster Relief
- 1. agile.open.connected Celery And The Social Networks 5 Things I Have Learned During Earthquake Hackathon Andrew Mleczko
- 2. Andrew Mleczko Python Dev RedTurtle - Italy - Poland amleczko@redturtle.it @amleczko www.redturtle.it Andrew Mleczko
- 3. May, 20th - the earthquake
- 6. the earthquake this is not “parmesan” this is real italian PARMIGIANO ;-D
- 7. re-start, do it fast!
- 8. and the real needs the virtual idea
- 10. keep attention alive online resources newspapers radio television
- 11. EARTHQUAKE 20/5 first idea 24/5engage stakeholders collect specs 28/5 get the server placeholder page 27/5 design layout 4/6 hackaton 11-14/6 find companies GOLIVE 26/6 36 days from event
- 12. facciamoadesso.it was born ;-)
- 15. Celery can fix all off it!
- 16. view from the top
- 17. The website architecture Notification App (REST) website stories ecommerce companies products news SMS Social Networks email github.com/RedTurtle/ restarter.buildout +
- 19. company profile
- 20. the product
- 21. book it!
- 22. The website architecture Notification App (REST) website stories ecommerce companies products news SMS Social Networks email github.com/RedTurtle/ restarter.buildout +
- 23. how to organize tasks?
- 24. how to organize tasks? small atomic minimal state
- 25. how to organize tasks? @task def post_on_wall(facebook_id, message): params = {} params['id'] = facebook_id params['message'] = message response = requests.post(url, params=params)
- 26. how to organize tasks? @task def send_sms(login, password, message, phone): payload = {'login': login, 'password': password, 'phone': phone, 'body' : message } try: r = requests.get('%s/send' % GATEWAY, params=payload, timeout=TIMEOUT) except requests.exceptions.Timeout as e: send_sms.retry(e, countdown=3)
- 27. rate limits
- 28. rate limits # make sure to not hit 3rd party limits @task(rate_limit=’1/m’) def send_sms(login, password, message, phone): ...
- 29. rate limits # make sure we will never spam our wall @task(rate_limit=’5/h’) def post_on_wall(facebook_id, message): params = {} params['id'] = facebook_id params['message'] = message response = requests.post(url, params=params)
- 30. rate limits gotchas ➡ Fails on worker daemon restart ➡ Doesn’t work with multiple worker daemons ➡ External rate limits are based on many factors: ➡ who’s asking ➡ public/private info ➡ what feature
- 31. rate limits gotchas https://api.twitter.com/1/account/settings.json 'x-ratelimit-class': 'api_identified', 'x-ratelimit-limit': '350', 'x-ratelimit-remaining': '257' https://api.twitter.com/1/users/search.json?q=europython 'x-featureratelimit-class': 'usersearch', 'x-featureratelimit-limit': '180', 'x-featureratelimit-remaining': '179'
- 34. lessons learned
- 36. Questions ? Andrew Mleczko Python Dev Plone Framework Team member amleczko@redturtle.it tw: @amleczko