On the shoulders of giants Learning About API Design by Looking Backwards
•Als PPTX, PDF herunterladen•
2 gefällt mir•836 views
Move forward with API Design by reviewing the lessons we’ve learned over the last 10 years with websites, SOA and product design.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie On the shoulders of giants Learning About API Design by Looking Backwards
Ähnlich wie On the shoulders of giants Learning About API Design by Looking Backwards (20)
Mehr von CA API Management
Mehr von CA API Management (20)
On the shoulders of giants Learning About API Design by Looking Backwards
- 1. On The Shoulders of Giants Learning About API Design by Looking Backwards Ronnie Mitra Principal API Architect - EMEA Layer 7 API Academy
- 2. Web APIs: New and Exciting! http://www.flickr.com/photos/every1knows/4191971139
- 3. “Web APIs? I’ve been doing that for years.” Image courtesy of http://www.flickr.com/photos/en321/3902138429/
- 4. Web APIs offer us a new perspective http://www.flickr.com/photos/mugley/4407790613
- 5. What can we learn by looking back? http://www.flickr.com/photos/dcassaa/483162086/
- 6. user-centered design makes things better
- 7. User-Centered Design: Design products for the users who will use them. User Interviews Rapid Prototyping Iterations
- 8. UCD helped drive websites into the world of web 2.0 Simpler look and feel Intuitive controls Familiar interfaces
- 9. UCD is all around us… and usually in our favourite products.
- 10. Can we apply a user centered design approach to web API design?
- 11. The challenge: Developers are a different breed of users. We need to work on a developer-centered design approach for APIs
- 12. Developer Centered Design Identify audience Make appropriate design decisions Prototype and test Iterate
- 13. removing barriers will increase adoption
- 14. We can learn a lot about registration from website design
- 15. Objective: Turn guest accounts into registered accounts
- 16. Principles of Registration: 1. Communicate the value of registering 2. Make it easy to signup 3. Provide instant feedback 4. Make policies clear 5. Use “lazy registration”
- 17. frictionless processes are good for API management.
- 18. security is war
- 19. Perfect security is not possible Practical security = Make attacks inconvenient and too costly to execute
- 20. Protecting Websites: 1. TLS/SSL for data privacy and server AU 2. User/password for authentication
- 21. Protecting SOA Services: 1. TLS/SSL for data privacy on the wire 2. WS-* for message security
- 22. OWASP Top 10: A1: Injection A2: Cross-Site Scripting (XSS) A3: Broken Authentication and Session Management A4: Insecure Direct Object References A5: Cross-Site Request Forgery (CSRF) A6: Security Misconfiguration A7: Insecure Cryptographic Storage A8: Failure to Restrict URL Access A9: Insufficient Transport Layer Protection A10: Unvalidated Redirects and Forwards
- 23. Is TLS/SSL Good Enough? You need to configure it properly. You need to use a secure implementation
- 24. Website design: password policies Don’t drive users away
- 25. The Lesson: Balance control with usability
- 26. hypermedia can make life easier
- 27. Links allow us to navigate the web
- 28. Forms provide a template for input
- 29. Links and templates can make an API easier to use
- 30. documentation is a craft
- 31. APIs aren’t just for the web What type of instructions do these APIs provide?
- 32. Think like a developer: Information must be accessible Provide information in small portions Think task based
- 33. Good documentation improves usability
- 34. Examples are like illustrations. Use a LOT of them.
- 35. effective management is critical
- 36. SOA Governance Enforce access control Promote service usage Provide service discovery documents Provide service usage visibility
- 37. API Management Enforce access control Promote API usage Provide API documentation Provide API usage visibility
- 38. SOA Governance How do we make sure that these services are used properly?
- 39. API Management How do we get people to use our API without falling over?
- 41. What can we learn from SOA Governance? Representing organizations is useful Complexity sucks Focus on the user
- 42. abstraction saves time and effort
- 43. In SOA, Enterprise Service Busses were useful (but complicated)
- 45. Off-loading security functionality makes sense
- 46. Provide consistent interfaces with a proxy
- 47. Summary There is gold to be found when looking back Don’t blindly lift and drop – adapt instead Always make your design relevant to your developers
- 48. On The Shoulders of Giants Learning About API Design by Looking Backwards Ronnie Mitra Principal API Architect - EMEA Layer 7 API Academy
Hinweis der Redaktion
- In many ways the web API space has become synonymous with a culture of modernity and hipness.
- Often times when speaking about APIs to architects who’ve “been around the block” you get a response that there is nothing new in this web API stuff.Maybe you felt that way? I know that in the early days, when I first heard the term I dismissed it as an attempt at rebranding existing technologies.
- From SOA We learned that many organizations are NOT greenfield and established patterns for integrating existing tech. outward.We can apply these patterns to the API management space.
- From SOA We learned that many organizations are NOT greenfield and established patterns for integrating existing tech. outward.We can apply these patterns to the API management space.
- From SOA We learned that many organizations are NOT greenfield and established patterns for integrating existing tech. outward.We can apply these patterns to the API management space.