An OpenAPI Service Dependency Vendor Extension
I’m working on a healthcare related microservice project, and I’m looking for a way to help developers express their service dependencies within the OpenAPI or some other artifact. At this point I’m feeling like the OpenAPI is the place to articulate this, adding a vendor extension to the specification that can allow for the referencing of one or more other service(s) any particular service is dependent on. Helping make service discovery more machine-readable at discovery and runtime.
To help not reinvent the wheel, I am looking at using the Schema.org Web API type including the extensions put forth by Mike Ralphson and team. I’d like the x-api-dependencies collection to adopt a standardized schema, that was flexible enough to reference different types of other services. I’d like to see the following elements be present for each dependency: https://goo.gl/DxhQX9 #DataIntegration #ML
The API Stack Profiling Checklist
ICYMI: I just finished a narrative around my API Stack profiling, telling the entire story around the profiling of APIs for inclusion in the stack. To help encourage folks to get involved, I wanted to help distill down the process into a single checklist that could be implemented by anyone.
The GitHub Base
Everything begins as a GitHub repository, and it can exist in any user or organization. Once ready, I can fork and publish it as part of the API stack, or sync it with an existing repository project. https://goo.gl/Nz2bhi #DataIntegration #ML