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
A Few Great Ways to Consume RESTful APIs in C#
ICYMI: By doing web development, you find yourself in the need to deal with external APIs (Application Programming Interface) sooner or later. In this article, my goal is to make the most comprehensive list of ways to consume RESTful APIs in your C# projects and show you how to do that with some simple examples. After reading the article, you will have more insight into which options are available to you and how to choose the right one next time you need to consume a RESTful API.
What Is a RESTful API?
So, before we start, you might be wondering what does API stand for, and what is the RESTful part all about? https://goo.gl/djwUyv #DataIntegration #ML