Home

Introduction OpenAPI Specification (formerly Swagger Specification) is an API description format for REST APIs. An OpenAPI file allows you to describe your entire API, including: v   Available endpoints (/users) and operations on each endpoint (GET /users, POST /users) v   Operation parameters Input and output for each operation v   Authentication methods v   Contact information, license, terms of use and other information. API specifications can be written in YAML or JSON. The format is easy to learn and readable to both humans and machines. In this article, I am going to explain basic Structure of OpenAPI Specification. Overview You can write OpenAPI definitions in YAML or JSON. In this guide, we use only YAML examples but JSON works equally well. All keyword names are case-sensitive. A sample OpenAPI 3.0 definition written in YAML looks like: Metadata Every OpenAPI specification starts with the openapi keyword mentioning the version of the specification fo

Introduction If you're looking for MuleSoft Interview Questions for Experienced & Freshers, you are at right place. There are lot of opportunities from many reputed companies in the world. According to research MuleSoft has a market share of about 5.9%. So, You still have opportunity to move ahead in your career in Mule ESB. There are different positions open as Mule ESB Developer, Mule ESB architect, Mule ESB engineer, Mule ESB consultant, Mule ESB expert, etc across many top IT hubs. Overview What is ESB? An enterprise service bus (ESB) is software architecture for middleware that provides fundamental services for more complex architectures. For example, an ESB incorporates the features required to implement a service-oriented architecture (SOA). In a general sense, an ESB can be thought of as a mechanism that manages access to applications and services (especially legacy versions) to present a single, simple, and consistent interface to end-users via Web- or for