Some think that with great effort it's possible to create Web APIs that never change. Yet these efforts always seem to be futile. Clients evolve at a different rate from the services they use and vice versa. This means that Web API developers must devise ways to accommodate new requirements while ensuring these changes do not break existing users. So how can services be designed to support both backward and forward compatibility?

In this session we'll discuss how Web API designers introduce breaking changes and how these can be prevented. We'll examine a few patterns that encourage graceful service evolution, and we'll also cover some anti-patterns that thwart this objective."