Videos %p Can't make it to the big conferences in Paris, London, or

San Francisco? we get it! We've all got local bars to keep up appearances at, bike races to train for, and pet turtles don't feed themselves!

Grab these mini conference talks, and watch then whenever you fancy.

Taking a Break from Dodgy Dependencies

Is your architecture an octopus orgy of unstable systems, where one domino

can fall and knock over everything else? This talk looks at timeouts, retries and circuit breakers, to add control to the chaos.

HTTP Caching

Mini conference talk covering HTTP caching, mostly caching client

responses via HTTP middleware to skip making requests the client already has fresh answers to, then using conditional validation to check if things have changed.

Conditional validation is one of the least understood but most powerful

features for HTTP, but it's simple when you get the hang of it!

Make your applications quicker, save mangling application servers when

you don't need to, and we'll even throw in some hints towards network caching to really help iron out stampeding herds.

A No Nonsense GraphQL and REST Comparison

Folks who don't understand what REST and HATEOAS mean keep acting like

GraphQL is somehow a replacement. It is amazing, and I'll explain why, but they're two different things, used for different things!
Get pragmatic API, HTTP and REST info monthly!
Not into mailing lists? Get all modern with Slack. We're the largest API-centric Slack channel around. Get your API, REST and HTTP questions answered by 2,000+ people.

About Phil Sturgeon

Since 2010 I've worked as a freelancer, consultant, Head of API, and CTO, for several API-centric technology startups.

Previously at Ride, I was given me the chance to work with amazing developers, including several Rails API contributors. We built an event-driven architecture with several REST APIs and a few RPC ones, and it was here I learned the benefits of REST being a state machine over HTTP.

Then at WeWork, I used my experience to help educate developers, define standards for API design and architecture, and work on open-source tooling for OpenAPI, JSON Schema, and HTTP. WeWork has 50+ APIs, and here I have had a chance to learn a lot about keeping distributed applications performant. Tmeouts, retries, circuit breakers, keep alive settings, and HTTP caching specificially.

I try to turn all of this learning into books, videos, and articles, so others can learn easily things I've had to learn the hard way.