Good to Great: API Design Patterns Beyond REST
Last year, my workshop on developer experience demonstrated how user experience design and research methodologies could significantly increase the quality and value of API products. The most frequently asked question I received after the workshop was, "But what are the best practices I should follow when designing my API?"
While there are too many important use-case details for general best practices, we can explore design patterns that popular APIs use and the situations where the patterns are successful (or not). As always, I'll share real-world user research of developers raving and raging about their experiences working with various APIs.
Additional Supporting Materials
- REST is a great architecture for basic CRUD on simple resources, but how does it scale? How should I handle complex, relational resources? How should I handle large collections (filtering, sorting, pagination)? What are some batching options for bulk read and write operations to reduce the number of API calls?
- How can the "options" method for HTTP and the hypermedia pattern help make my API easier to work with?
- How can middleware help me build a better API by understanding how endpoints are used? (Think KISSmetrics for APIs.)
- How do I improve an API design when developers are already using the current design? We'll look at migration and versioning strategies.
- How can I best use webhooks to improve application and API provider performance?
- Jeremiah Cohick Fitbit
Jeremiah Cohick Fitbit
Show me another