Developing APIs with OAS and Swagger Codegen

Developing APIs with OAS and Swagger Codegen


Now let’s start to talk about how
definitions touch the development phase of your API lifecycle. So cogeneration
is something that’s become incredibly popular as well and especially with
tools like the Swagger coach, which is one of the most popular tools in the
swagger ecosystem so from the open API defined definition of your API you can
actually generate server stubs and client as decays directly. What do I mean
by this? Well let’s take for example you have your open API specification from
here I’m using say a code generating tool like swagger CodeGen. you can
actually generate server stubs in over 30 different languages which your
developer your internal stakeholder who builds out the API who can then use that server stub and instead of worrying about any of the boilerplate code they
can focus only on the business logic because what the code generator does
is it abstracts all of that manual routing the configuration the you know
essentially all that boilerplate code which people have to worry about and it
gives you this nicely packaged code base which your developer can then go in
and focus just on the business logic and build out a solid API. It minimizes so much
time, reduces so much time, and minimizes the effort and then we have the consumer
from your code generation you can actually also generate SDKs. SDK’s
a big problem. I’ve heard so many clients who tell me how incredibly hard
it is to build SDKs in so many different languages, Client SDK specifically
because there’s so many different programming languages and everyone wants
has the different need so with the Swagger CodeGen project you can also
auto-generate SDKs in over 40 languages which is a large
amount of program programming languages which the consumers can then use again.
All of this is open source you can actually go in anytime and start using
them so the advantages of Swagger CodeGen of course is or just cogeneration from
the definition is no wasting time on boilerplate code, right. Once you have the
definition in place from the definition itself you can auto-generate the server stops or the client SDKs no wasting time on boilerplate code let’s
just get straight to the point let’s focus on the value of the API and
not spend time on manually configuring that APIs routing. Faster
prototyping get to your value as soon as possible.
And finally out of the box, SDK generation for easy consumption. You can
ensure that you have SDKs right out of the box
which your end consumers can then use to start, you’re consuming that API,
integrating that into their own applications, and essentially makes for a
great developer experience as well. And the tool that supports us is the Swagger
CodeGen project which you can find on swagger.io

One thought to “Developing APIs with OAS and Swagger Codegen”

  1. Great stuff, I am so pleased to have come over this, from what I understand, this appears to be able to do almost everything of what I have been looking for to generate both c# and ts boiler script code for angular, my repository layer, the view models and maybe even the boiler script parts of my business layer as well as ease and enforce globalization and test coverage of my app so I hopefully only end up designing the architecture, write the templates and implement specific business rules for selected business objects. Did I understand you right? Can I customize code gen templates and maybe even run multiple templates on each entity?

Leave a Reply

Your email address will not be published. Required fields are marked *