Creating the contract with your consumers is the first thing you do.
- You can automatically create your API from this OpenAPI definitions (e.g. skip the whole configuration of your API Gateway on AWS by using OpenAPI)
- You’ll have a beautiful visual overview of your API
- Generate your class definitions based on this OpenAPI definitions
- Validate incoming and outgoing requests with the OpenAPI definition
Did you notice that I just gave you five advantages of using OpenAPI? It’s only the beginning. And that’s why you should practice API First development with OpenAPI.
Nick Van Hoof Passionate cloud developer, sports athlete, boyfriend
Blogs:
– https://ordina-jworks.github.io/cloud/2019/01/14/Infrastructure-as-code-with-terraform-and-aws-serverless.html
– https://ordina-jworks.github.io/cloud/2018/10/01/How-to-build-a-Serverless-Application-with-AWS-Lambda-and-DynamoDB.html
– https://ordina-jworks.github.io/development/2018/11/20/mongodb-europe-018.html
– https://nickvanhoof.com/docker-compose-wordpress/
– https://nickvanhoof.com/ocp/
– https://nickvanhoof.com/aws/
https://gitlab.com/nxtra?nav_source=navbar
The post Why you should use OpenAPI for your API design appeared first on JAXenter.
Source : JAXenter