Vladimir Oane
•
0 likes•410 views
The document describes the four phases of building a conversational graph database that can handle large-scale web traffic. Phase 1 involved a prototype with two servers and PHP/MySQL that had issues with distribution and performance. Phase 2 added Amazon servers and Python with SimpleDB and SQS but had database slowness and workflow problems. Phase 3 introduced a RESTful API with Tokyo Cabinet and handled millions of calls per hour with no issues. Phase 4 added search capabilities by indexing millions of items per day but required large Amazon servers for speed. Each phase addressed problems from previous phases to improve scalability and performance.
More Related Content
Viewers also liked
Similar to Vladimir Oane
Similar to Vladimir Oane (20)
More from evensys
More from evensys (20)
Recently uploaded
Recently uploaded (20)
Vladimir Oane
- 1. Experiences in web scalability Thursday, September 17, 2009
- 2. uil ding B Conversational Graph Thursday, September 17, 2009
- 3. Social Graph Professional Social Graph Message Graph Thursday, September 17, 2009
- 4. Thursday, September 17, 2009
- 5. Thursday, September 17, 2009
- 6. Thursday, September 17, 2009
- 7. Database of threaded, platform independent conversations that you can find and track in real time. Thursday, September 17, 2009
- 8. Database of threaded, platform independent conversations that you can find and track in real time. m e so w e Thursday, September 17, 2009 A
- 9. Phase 1 The prototype Thursday, September 17, 2009
- 10. Tracking on demand Few friends as users Thursday, September 17, 2009
- 11. 2 servers PHP + MySQL Nothing special Thursday, September 17, 2009
- 12. Problems: •No easy way of distributing the shit on many machines •Crapy database •PHP sucked at things like parallel processes Thursday, September 17, 2009
- 13. Phase 2 Beta phase Thursday, September 17, 2009
- 14. s till Tracking on demand 1000 beta users Thursday, September 17, 2009
- 15. Amazon servers Python baby Simple DB SQS Thursday, September 17, 2009
- 16. Queue (SQS) Module Module Module Server … Server Server Database (Simple DB) Thursday, September 17, 2009
- 17. Problems: •The database was slow and expensive •Bad web-app workflow Thursday, September 17, 2009
- 18. Phase 3 The API Thursday, September 17, 2009
- 19. s till Restful API Millions calls/h Thursday, September 17, 2009
- 20. Tokyo Cabinet Mashery Thursday, September 17, 2009
- 21. Problems: No problems yet Thursday, September 17, 2009
- 22. Phase 4 Search Thursday, September 17, 2009
- 23. Tracking the web Indexing millions items/day Thursday, September 17, 2009
- 24. Large Amazon servers Customized Search engine Load balancers Thursday, September 17, 2009
- 25. Problems: •Speed -> we need huge machines Thursday, September 17, 2009
- 26. Thursday, September 17, 2009