Measuring REST: Make the Case for Constraints
•
1 gostou•663 visualizações
Slides from my talk at restfest 2011.
Recomendados
Recomendados
Mais conteúdo relacionado
Semelhante a Measuring REST: Make the Case for Constraints
Semelhante a Measuring REST: Make the Case for Constraints (20)
Mais de Subbu Allamaraju
Mais de Subbu Allamaraju (16)
Último
Último (20)
Measuring REST: Make the Case for Constraints
- 1. Measuring REST Subbu Allamaraju http://www.subbu.org http://twitter.com/sallamar
- 2. My (Im)Maturity Level 1: What is REST? Level 2: Wow! … What? … Aha! Level 3: Explain, rationalize Level 4: Build stuff
- 4. Hypermedia and Media Types
- 5. How to measure REST? What to measure?
- 10. 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
- 12. • But “glory” is not a systemic quality. • Glory is not measurable • Does not lead to $$$
- 14. Show me 100% RESTful apps
- 15. Is REST a hoax then?
- 16. Question #1: Is this a marketing or messaging problem?
- 17. Question #2: Can you prove that sum(constraints) leads to sum(qualities)?
- 18. Hand-wave Reason out and rationalize in the abstract Nah, we need to put some engineering back into software
- 19. Question #3: Can you prove that any given constraint leads to any quality?
- 20. Hand-wave Advocate: “Make judicious tradeoffs” But how do I know if I’m making judicious tradeoffs?
- 21. Step #1: Agree on a set of qualities that matter for your app
- 23. Ex: • Performance • Ease of use • Adoption Roy’s list is not the super-set
- 24. Step #2: Contextualize the qualities into scenarios
- 25. • 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
- 26. Step #3: Prioritize qualities and scenarios
- 27. • 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
- 28. Step #4: Pick solutions among alternatives that you think meet the scenarios
- 29. • 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
- 30. What should you measure? $$$ $$$,$$$ $$$,$$$,$$$ Make the case for REST constraints based on specific scenarios and priorities