Measuring REST

887 views

Published on

Slides from my talk at restfest 2011.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
887
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
5
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Measuring REST

  1. 1. Measuring REST Subbu Allamaraju http://www.subbu.org http://twitter.com/sallamar
  2. 2. My (Im)Maturity Level 1: What is REST? Level 2: Wow! … What? … Aha! Level 3: Explain, rationalize Level 4: Build stuff
  3. 3. Hypermedia and
   Media Types
  4. 4. How to measure REST? What to measure?
  5. 5. 100  %  REST?   Performance – network performance, user perceived performance, and network efficiency Scalability Simplicity REST Constraints Modifiability – evolvability, extensibility, customizability, configurability, and reusability Visibility Portability Reliability
  6. 6. •  But “glory” is not a systemic quality. •  Glory is not measurable •  Does not lead to $$$
  7. 7. Show me 100%RESTful apps
  8. 8. Is REST a hoax then?
  9. 9. Question #1: Is this a marketing or messaging problem?
  10. 10. Question #2: Can you prove that sum(constraints) leads to sum(qualities)?
  11. 11. Hand-wave Reason out and rationalize in theabstract Nah, we need to put some engineering back into software
  12. 12. Question #3: Can you prove that any given constraint leads to any quality?
  13. 13. Hand-wave Advocate: “Make judicioustradeoffs” But how do I know if I’m making judicious tradeoffs?
  14. 14. Step #1: Agree on a set ofqualities that matter for your app
  15. 15. Ex: •  Performance •  Ease of use •  Adoption Roy’s list is not the super-set
  16. 16. Step #2: Contextualize the qualities into scenarios
  17. 17. •  Performance •  Serve a photo in “t” msec •  Process “n” photos per hour •  Ease of use •  A developer should be able to build a client app in 30 minutes •  Adoption •  Must gain “y00” developers in 3 months after launch
  18. 18. Step #3: Prioritize qualities and scenarios
  19. 19. •  Adoption •  Must gain “y00” developers in 3 months after launch •  Performance •  Serve a photo in “t” msec •  Process “n” photos per hour •  Ease of use •  A developer should be able to build a client app in 30 minutes
  20. 20. Step #4: Pick solutions amongalternatives that you think meet the scenarios
  21. 21. •  Adoption •  Must gain “y00” developers in 3 months after launch •  Performance •  Serve a photo in “t” msec •  Process “n” photos per hour •  Ease of use •  A developer should be able to build a client app in 30 minutes
  22. 22. What should you measure? $$$ $$$,$$$ $$$,$$$,$$$ Make the case for REST constraints based on specific scenarios and priorities

×