In previous posts in our series about the API facade pattern, we looked at the basic steps to implement an API facade as well as at common patterns. This time, we'll start exploring the technologies at the heart of implementing an API facade. We'll begin with the set up involving DNS, Cloud Platform, Web server, app server, API Gateway and subdomain routing.
Thanks to all who participated in the HATEOAS 101 Webinar this week. The video (~30 min.) and slides are below. Check them out for an introduction to the core principles, examples, and a look at the value of the approach for API providers and app developers. Thanks @landlessness.
Thanks to all who participated in the fourth and final episode in the Webinar Shorts series on the API Facade pattern. The fourth episode covers people considerations—the team structures, the roles and responsibilities and the politics—for building and using an API facade. The video (~22 min.) and slides are below. Thanks @landlessness.
In the Webinar and blog posts about the API Facade pattern, we've talked about API facades that make it easy to provide access to internal systems, and a lot of companies use a facade in this mode.
In this post in our series about common patterns in the API facade, we'll look at patterns for designing versions and data formats. We'll focus on designing for a scenario in which you need to support more than one version. This is common scenario especially in certain phases of your API's life cycle. The way to handle this with a facade is to design it such that regardless of which request comes into the facade, you have a shunt in place that points the request to the proper internal system, which serves the response.
In our series about the API facade we've already looked at the basic steps to implement an API facade and started examining common patterns by looking at errors.
This time, we'll look at a couple more common patterns: data stubs and URLs.
We've recommended that the best solution to the problem of exposing complex back-end systems' functionality in a way that's useful for app developers is to implement an API facade pattern. In a previous post we looked at the basic steps to implement an API facade. In the next few posts, we'll examine common design patterns and the problems that the different patterns solve. We'll cover six common patterns: errors, stubs, URLs, versioning, data formats, and internal and external systems.