Currently around 30 companies are active member of OpenAPI initiative. These ten companies were the founding member of OpenAPI initiative: 3Scale, Apigee, CapitalOne, Google, IBM, Intuit, Microsoft, PayPal, Restlet and SmartBear. In December 2015, Swagger specification was donated by SmartBear to a new open-governance organization, set up under Linux foundation: the OpenAPI Initiative. In March 2015, SmartBear Technologies acquired interest in Swagger intellectual property & other open source technologies from Reverb Technologies.
Swagger specification 2.0 was published in September 2014 with lot of changes & improvement. This was the first version to gain widespread adoption across the API industry, and is still in use by some API providers today. In March 2014, version 1.2 was published which was more inclined towards JSON Schema Draft 4 standard. In August 2012, he published version 1.1 of Swagger spec while working at Reverb Technologies. In 2009, a guy called Tony Tam started working on creating a API specification standard what would become Swagger API specification. So you can standardize API design across teams hence cutting down time on developers’ effort to understand each API in a different way.
#Swagger editor what is a date code#
A tools ecosystem can be built around this standard which can auto validate the API design, auto generates code & documentation, enhance security for all API. Organisation should have a common standard so that all developers understand the API descriptions & documentation without gaining specialised knowledge for each & every API, API design review becomes better when everyone follows the same standard. Don’t delve into implementation quickly, spend enough time on designing the API, rectify all possible mistake first.
But once you start designing API for larger audience in a enterprise company or consumer internet company, you can’t so easily get away with such minimalist design, a lot of stake holders / teams are involved in the process, a lot of systems might get involved, so a homogeneous & consistent design strategy has to be developed which every stake holder in your organization ( even outside organizations as well ) can relate & contribute to. This strategy works in small to mid-size companies or startup companies.
#Swagger editor what is a date series#
We jot down just all necessary request & response (in most of the cases HTTP Code 200 series response) parameters in a document, get it reviewed quickly, accordingly we create some resource models & jump into implementation. Generally when we write REST API, we focus a lot on implementation & very little time on designing the proper request / response schema, API resource models. The article does not describe what REST API is, rather you should have some basic knowledge about REST API before going through the article.
Disclaimer: I presume we all have written one or multiple API at certain point in time in our career, otherwise you would not have bumped into this article.
0 kommentar(er)
