Building APIs can be easy right, we design the data model, slap some routes in and controllers to wrap our ORM access.
But is this efficient, and does it scale? What happens when our application grows to a point where we have 100s of Models and more scopes than your average game of Call of Duty? How can we structure and approach our APIs in Laravel, so that scale from a code perspective isn't an issue?
In this talk I will take you through how I approach this problem, and have been approaching this problem for the last few years.