Busy or Lazy?: Design API in Anypoint Studio
Using Anypoint Studio 7.7 and later, we can create API specifications and fragments directly in our Anypoint Studio, or create API Specs in Design Center to be imported.
Join the DZone community and get the full member experience.
Join For FreeCreating API design using Anypoint Studio is a cool feature added by MuleSoft.
Now we can create API design from the comfort of our home, i.e., our Anypoint Studio. We can also test using Mocking Service and publish API Specs to Exchange from Anypoint Studio. No need to login to Anypoint Platform, again and again, to make changes in API Specs.
Interested in creating/updating the API Design Specs using Anypoint Studio? Well here is what this is all about:
API Specs in Anypoint Studio
Using Anypoint Studio 7.7 and later, we can create API specifications and fragments directly in our Anypoint Studio. The API Specs can ALSO be first created in Design Center and then imported into Anypoint Studio.
Any changes made in Anypoint Studio are reflected in Design Center and v.v.
API specifications in Anypoint Studio and Design Center are synchronized using Version Control System. Git is used to track the API Specification changes and Anypoint Platform has a Git repository for our API specifications. The Git repository helps to synchronize changes between the Design Center and Anypoint Studio.
From Anypoint Studio, we commit our API spec, fragments, etc., to the Remote Git Repository of Anypoint Platform and these changes are then reflected in the Design Center. If we go ahead and make changes in the Design Center, the changes are pushed to the remote repository automatically and we can pull those changes in our Anypoint Studio.
Come and Learn With Me
So this is a shout-out to people like me who are sometimes busy and sometimes lazy; let's now design easily in Anypoint Studio. View my video for an overview of this feature. In this video, I am creating an API design using RAML 1.0 in Anypoint Studio:
Happy Learning!!
Opinions expressed by DZone contributors are their own.
Comments