π€ Looking At The API Life Cycle Through The Lens Of A Municipal Transit System
- π€ Kin Lane
As we move beyond a world of using just a handful of internal and external APIs, to a reality where we operate thousands of microservices, and depend on hundreds of 3rd party APIs, modern API infrastructure begins to look as complex as a municipal transit system. Realizing that API operations is anything but a linear life cycle, letβs begin to consider that all APIs are in transit, evolving from design to deprecation, while still also existing to move our value bits and bytes from one place to another. I would like to share with you a look at how API operations can be mapped using an API Transit map, and explored, managed, and understood through the lens of a modern, Internet enabled "transit system".
This page was generated from this YAML file. Found a typo, want to add some data? Just edit it on GitHub.