In this video, we will look more closely at Swagga and open API.
I know the differences between them, although we have covered this a bit before.
I wanted to explain it in a separate lecture, as it is very important to know the difference between
these two domes.
There is some confusion among developers, managers and others.
When it comes to Swagga and open API, you may be finding it hard to know the exact difference between
them.
He also might be wondering whether you should use the term Swagga are open API when referring VBS.
This Laguerre should clear that confusion.
In short, the term Swagga refers to the tools provided by the Smart Beer Company, whereas Waban API
refers to the EPA specification defined and maintained by the Open API initiative.
The confusion arises when Smart renamed Swagger API specification to open API specification until version
2.0, not zero.
It was referred to as Swiger specification, however, from 3.0 not zero, it is referred to as open
API specification.
This document that you see here is referred to as open API specification.
You can either use Yamal or Jessan to define an open API document.
It has got metadata about the API, such as Russian information about the API external document references
back to group operations, bots that define operations on various resources and so on.
The tool that was used to create this open specification is swagga.
Ed, in this case, swagged Ed is just a tool used to develop open API documents on the right hand side.
We have another tool from Swagga, namely Swagga UI.
This shows the open API specification in a nice Yuya format that is easy to understand.
It shows the operations defined against various resources.
Also, you can try out the operations defined using the same UI.
If you go to the Swagga website, we can understand the main purpose of Swiger.
It is primarily used for API development.
It refers to the set of open source and professional tools provided by smart beer when we open up the
tools menu at the top.
We can see the complete list of tools provided by Swagga.
Swagger has two broad categories of tools swagger, opensource and swagger.
Among the open source tools we have swagger, Gourgeon, Swagger, Ed and Swagger UI.
These are free to use among the professional tools we got swagger hub for teams and swagger for enterprise.
These are tools that better yapper management in the corporate environment.
However, not that we can use any of the tools while working with the open standard.
Swagga tools are just one set of tools.
Many other third party vendors provide various tools to work with open API.
Since all these tools follow certain standard guidelines and specifications, they are compatible with
one another.
Has Swagga had been around from the beginning?
It is well known and used to more than other tools.
When it comes to creating the open API specification, there are two ways to achieve it.
Design first and code first.
Let us look at them in the next video.