![]() Designing the API Specsįor the design phase of the life-cycle, we have two options in the Swagger toolchain. ![]() Since we will be using Swagger tools, please go ahead and create an account on Swagger.io. Note: If you are interested in creating your own API spec from scratch, please use the Swagger Editor. ![]() The focus of the article will be to go through the lifecycle of API development. In the interest of time, we will be using the PetStore API as our sample API. We will explore using the Swagger toolchain to design, build, document, test the API and enable standardization of the API across teams in the organization.Ĭheck out my previous post comparing various API Platforms and Specification formats.Ĭredit: swagger.io Life-cycle of creating an API In this post, we will look at the end-to-end lifecycle of a REST API. Instead of declaring a winning design style, I believe that each one of these design styles stands their ground, and it depends on the use case when to use which style. ![]() We have been building APIs for ages, with varying standards and design styles - SOAP web services, gRPC, REST, and until recently GraphQL. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |