Randy Shoup shares war stories from eBay and Google about performance, consistency, iterative development, and autoscaling, connecting them with experiences building KIXEYE's gaming platform.
Sid Anand uses examples from LinkedIn, Netflix, and eBay to discuss some common causes of outages and scaling issues. He also discusses modern practices in availability and scaling in web sites today.
Sastry Malladi discusses the performance implications of using various data formats and versioning across eBay, showing the results of certain benchmarks concluding that JSON is the best format.
Randy Shoup shares 10 lessons learned from eBay: Partition Everything, Asynchrony Everywhere, Automate Everything, Everything Fails, Embrace Inconsistency, Expect (R)evolution, Dependencies Matter, Respect Authority, Never Enough Data, Custom Infrastructure.
Sastry Malladi presents different ways used by the industry to implement a RESTful SOA, detailing how eBay did it in order to achieve performance, and what lessons can be taken from that.
Beside casual challenges met in implementing SOA, Sastry Malladi talks about additional ones encountered while implementing large scale SOA deployments, giving eBay as example of an efficient, extensible and scalable SOA platform accompanied by an automated governing process.
In this presentation, Dan Pritchett addresses latency issues in web applications that should be dealt with from the beginning when the system is designed. Dan offers some practical solutions to latency.
In this presentation filmed during JAOO 2007, Wayne Fenton, Director of Architecture at eBay Inc., talks about the ways in which software architects can design systems for much-improved efficiency and reliability from an operational perspective.
Randy Shoup covers the architectural principles eBay has used to grow and evolve its infrastructure to massive scale. It covers the forces ("-ilities") needed to contend with and design for scalability, availability, manageability, etc. He outlines eBay's architectural principles which meet - and trade off - those forces and describes reusable patterns for each strategy with eBay examples.
You're confident that your software will handle horizontal scale to thousands of servers. But how about your operational team? Have you also architected for managing that large collection of servers? Dan Pritchett will present lessons learned at eBay and lead a discussion on how to ensure your transactional scalability doesn't ignore your architecture's manageability