Lazy-Loaded Scale (Involver Tech-Talk)

For maximal customer value, lazy load everything.

Tests before code ensure that you write the right thing. Beta stage products ensure that you write the right thing. Performance testing (at every stage) ensure that you write the right thing.

In pursuit of the right thing. Happy coding!

Transcript

1. Conversation Suite Patterns and Paradigms
2. Be Agile to the Core We don't need to ship a finished product.
3. Know the Problem ... and fix only that which is broken
4. Key Technology Persistence Filtering API Application
5. Key Technology MySQL Solr Rails Backbone
6. now with some context on the stack
7. Performance and Scalability 1. Responsiveness - as observed by the user 2. Maintain an SLA - volume before one-way violation
8. Responsiveness
9. Responsiveness What are the application's needs. api.respond_to?(:various_loads)
10. Responsiveness Solr MySql
11. Responsiveness Response 523 ms Throughput 330 rpm
12. Responsiveness Response 1552 ms Throughput 660 rpm
13. Performance and Scalability 1. Responsiveness - as observed by the user 2. Maintain an SLA - volume before one-way violation
14. Maintain an SLA Messages & Comments: 1 minute
15. Maintain an SLA • Facebook Batch API • Authorized Twitter Accounts • Twitter Searches :(
16. Maintain an SLA We care about only one thing... When do we violate the SLA?
17. Maintain an SLA Separation of Concerns github.com/involver/facebook-graph-api-mock 1. lots of data 2. lots of users 3. lots of both
18. Takeaways 1. Find out what you care about. 2. Mock everything you don't. 3. Lazy-loaded Scale