Description
What do I wish I’d known when I first developed an app using application programming interfaces? Getting the architecture of your app right is important—and if you’re building an app that consumes APIs, this 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.
Key Learnings
- Learn how to structure a well-designed API heavy application
- Learn about resilient API consumption patterns
- Learn how to refactor your own applications to use best practices
- Continue your API best practice learning with resources provided