Evaluating SwaggerHub. Basic Questions
We have seen the demo (video), but I still have some questions about SwaggerHub that other users might have the answer for:
- Does SwaggerHub have any data catalog built-in? The goal here is to detect new fields being introduced when creating new or changing existing APIs. The developer creating the API would get a list highlighting the fields that don't yet exist in the DATA CATALOG. For example, the developer chooses person-code, and SwaggerHub lists this field as a new one, and then the user can go through the data catalog and find the person-id and a description for this field. This data catalog feature would reduce the chance of APIs using different names for the same semantic field.
- Can SwaggerHub support different standards for different sets of APIs? For example, let's say SYSTEM APIs (not exposed to the internet) and BUSINESS APIs (exposed to the internet)?
- Is it possible to automate as much as 60% of the API validation with SwaggerHub? We are a growing company, and it's getting harder to ensure that so many APIs, coming from different teams, are well designed and CONSISTENT across the company.
- Does SwaggerHub support any other API type? Like GraphQL or GRPC?
Any help would be much appreciated.