Abstract

In this session we will describe the best practices for writing durable apis and PHP: how would you design services that need to be stable, evolvable and easily maintainable for years without the hassle of (too much) refactoring? How do you ensure you pick the correct patterns and technologies that won’t be outdated in the upcoming months? How to glue your APIs in a single response and still make it perform in milliseconds?

Writing apis is cool, maintaining them is usually a pain.