When you've been tasked with creating an HTTP API, there's many things that you need to consider and I'm here to help you navigate your journey. We start with the fundamental decision of architecture: should your API be RESTful? What about GraphQL? or RPC? We'll look at the choices and their strengths and weaknesses to guide your decision. We'll also take a hard look at the other, vital components of an API from how it works with HTTP, through validation, payload formats and error handling. An API makes its mark when it is used, so we'll also consider developer experience to ensure that your API is best it can be. By the end of this talk, you'll be well-placed to design and deliver a great API that's fit for purpose.


Comments are closed.

Gene Surov at 12:01 on 19 May 2022

Rob is trying himself in a philosopher role-play 😂

He had an unique style and was crystal clear.
The topic was interesting, highlighting the differences between RPC, REST and GraphQL.
The rule of software design: "it is always hard".

James Titcumb at 12:21 on 19 May 2022

Great insight into comparison of API styles. Rob is excellent at speaking.

dParadiz at 13:26 on 19 May 2022

Well structured talk , but mostly basic.

Great in-depth look at the topic

Gregor Novak at 09:08 on 20 May 2022

Presented API styles in a clear and concise manner.

Matteo Contri at 09:18 on 20 May 2022

The talk is too much philosophic about API design choices in general instead of give some more pragmatic guidance

Experienced talker, very pleasant to listen to. Would be interesting to see where MS Graph and JSON-API fit in.

Great speaker and good content

Interesting talk, maybe a bit generic 😊

The talk was alright in contents and delivery, though I was personally hoping for something a bit beyond the basics which were discussed.

Andrea Sprega at 22:38 on 22 May 2022

Interesting talk, maybe a little bit too generic and sometimes a bit "slow" as to how it was presented. Could have been better with some more practical examples.

well done - I liked how you don't claim REST or GraphQL is generally superior but explain the benefits and drawbacks of each.

the critical comments here on joind.in might come from expectation management - this was not a technical talk on how to do REST/GraphQL, but a comparison of the approaches.

A lot of information packed into this session. I've done a lot of work on API's, mostly on REST API's, but this talk convinced me that I need to dig into GraphQL as well some time soon.