Best practices when structuring an API heavy app

What I wish I knew when I first developed an app using APIs - getting the architecture of your app right is important - and if you are building an app that consumes APIs this is can be even more critical. By using techniques to separate out the code that connects to the API from what matters most - your business logic - you can easily build testability, resiliency, and flexibility around the API you consume - while keeping your business logic free from API changes. You will leave this talk with examples of why this separation is important, specific examples of patterns to use, and what to anticipate could go wrong when good patterns are not used.