Breaking Postman API Collections Into Meaningful Units Of Compute
I’m fascinated with the unit of compute as defined by a microservice, OpenAPI definition, Postman Collection, or any other way of quantifying an API-driven resource. Asking the question, “how big or how small is an API?”, and working to define the small unit of compute needed at runtime. I do not feel there is a perfect answer to any of these questions, but it doesn’t mean we shouldn’t be asking the questions, and packaging up our API definitions in a more meaningful way.
As I was profiling APIs, and creating Postman Collections, the Okta team tweeted their own approach to delivering their APIs at me. They tactically place Run in Postman buttons throughout their API documentation, as well as provide a complete listing of all the Postman Collections they have. Showcasing that they have broken up their Postman Collections along what I’d consider to be service lines. Providing small, meaningful collections for each of their user authentication and authorization APIs: https://goo.gl/htKeuY #DataIntegration #ML