PRO WORKSHOP (API): Good APIs - More than Just a Payload Definition

API World -- PRO Stage 1
Join on Hopin

Phil Wilkins
Capgemini UK, Snr Consultant and Design Authority - PaaS, Author & Blogger

Phil Wilkins has spent over 25 years in the software industry with a breadth of experience in different types of businesses and environments from multinationals to software startups and consumer organizations including a global optical and auditory healthcare provider. He started out as a developer on real-time mission critical solutions and has worked his way up through technical and development leadership roles primarily in Java based environments.

Phil now works for Capgemini specialising in cloud integration and API technologies as part of a multi award winning PaaS team in the UK. Phil’s role is both client facing with well know national and international brands, as well as supporting the wider practice with technical expertise and leading the innovation initiatives.

Phil has supported the development of technical books (Packt Publishing, Thomas Erl (Prentice-Hall) etc) including co-authoring the books Implementing Oracle Cloud Integration and Implementing API Platform. He has also had a number of articles published in technical journals in his own right as well as being an active blogger. When not writing Phil is a co-organizer of the London Oracle Developer Meetup and driving force behind the Drones with APIs project.

Phil is TOGAF certified and recognised by Oracle as part of their Ace community.

When defining APIs the most common considerations are from what our payload looks like, and then from a implementer perspective. However, good APIs whether they’re internal or public are far more than just a payload description and need a consumer’s perspective. In this session we look at what makes up a good API; from OWASP Top 10 implications to ISO and data definitions, to how to make it easy for your consumers, why these points are important and the implications. We’ll explore techniques to overcome of the challenges seen when producing good APIs. Whilst we all think we know how to define APIs, you’ll be surprised at the things that get overlooked or opportunities to be better.