Please log in to watch this conference skillscast.
In the last years API spread out around the world. Every modern application provides or consumes at least one API. It became very easy to setup an API, but it became even easier to build APIs no one really wanted to use. To provide an API is not a unique selling point anymore. Especially if you are providing a public API, your API should be so user friendly that your mom could use it or at least an inexperienced developer who never used an API before.
As an independent software engineer Michael has worked with various clients designing, building, testing, maintaining and even redesigning private and public APIs; starting from a simple API for Single-Page-Application to a highly scalable and complex kickass API serving millions of users every day.
In this talk Michael will share his experience from these projects giving some guidelines on API design and answering some questions which occur in every API project like "How can we provide this operation and still being RESTful?" or "How should we version our API?". Besides an admirable API Design Testing, Documentation and Mocking are always sticking points, which Michael wants to demystify by sharing his handy approach to creating an awesome developer experience.
With this talk you will be inspired to apply some of these techniques in your next API project.
YOU MAY ALSO LIKE:
- TDD for APIs in a Microservice World (SkillsCast recorded in November 2016)
- droidcon London 2019 (in London on 24th - 25th October 2019)
- µCon London 2020 - The Conference on Microservices, DDD & Software Architecture (in London on 27th - 29th May 2020)
- The Sonic Contender (in London on 28th October 2019)
- Lightning Talk: Ideas for Future Haskell Tooling (SkillsCast recorded in October 2019)
- How to Break Builds and Influence People - Ordnance Survey's Ongoing Cloud Native Journey (SkillsCast recorded in September 2019)
How to build an API your developers will love?
Michael worked as an independent API specialist for many years. He advised his clients in terms of API design, authorization standards, development processes and the implementation itself.