An OpenAPI Service Dependency Vendor Extension
ICYDK: 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/4KcN3V #DataIntegration #ML
REST API Testing With Spring Cloud Feign Clients
ICYMI: What Is Spring Cloud Feign?
Spring Cloud Feign is a convenient way to test your application’s API, focused on creating tests to verify business logic instead of spending time on the technical implementation of web services clients.
You only need to describe how to reach the remote API service by providing details such as the URL, request and response body, accepted headers, etc. The Feign Client will take care of the implementation details. https://goo.gl/75RFN1 #DataIntegration #ML