Kovair REST API – Bipin Shah’s Interview on Outlook Series

Listen to this article

Questions & answers and audio interview on Kovair REST API with Bipin Shah, CEO & Chairman of Kovair Software


Q 1. When was the concept of ESB first introduced and what are its benefits?

Ans: An Enterprise Service Bus (ESB) is fundamentally an architecture. It is a set of rules and principles established with the objective of integrating numerous applications on a single bus-like infrastructure. The ESB concept came into the market early in the year 2002. Benefits: Based on experience here at Kovair, the key advantages of using an ESB are less about features and functions and more about how one uses it. Some of its key benefits are as follows —
  • Scales from point-to-point solutions to enterprise-wide deployment (distributed bus).
  • 100% configuration and 0% requirement of hardcode coding.
  • Highly scalable and reliable.
  • Easy plug-in / plug-out and loosely coupling system.
  • Support for routing and mediation.

Q 2. What is API?

Ans: API is the acronym for Application Programming Interface. A software intermediary, Kovair API enables two or more applications to communicate with each other. It consists of a set of endpoints that allow one to externally execute the needful activities within an application. Kovair API is a Restful API that adheres to the principles of REST without involving the interference of the client. It supports http, https, TLS 1.1 or TLS 1.2 encryption.  

Q 3. To what extent have APIs achieved market acceptance?

Ans: The benefits of the Restful API in the software development ecosystem are profound. Over the last few years, the industry has seen a major market move from other API’s (such as SOAP and COM to name a few) towards REST.  

Q 4. What are the benefits of REST API-enabled products?

Ans: REST API-enabled products offer some of the following benefits:
  • Availability of multiple data formats, where SOAP supports XML only.
  • Superior performance.
  • Widely used protocol popular among major brands such as Yahoo, eBay, Amazon, and Google.
  • Limited bandwidth usage.
  • Uniform interface for data transfer. The REST system applies specific actions (POST, GET, PUT and DELETE) on the resources.
  • More visibility, reliability and scalability from an integration stand point.
  • More flexibility and portability.

Q 5. Does this mean the end of middleware integration solutions?

Ans: ESB is a middleware. Therefore, it is difficult to discuss the difference between a middleware and an ESB. Middleware acts as a bridge between applications. An enterprise service bus (ESB) on the other hand, implements a communication system between mutually interacting applications in a service-oriented architecture (SOA).  

Q 6. How do APIs make data integration easier?

Automation: The primary benefit of API is automation. Thus, any manual time-consuming job like feeding data to an application or extraction of data based on a query can be achieved in minutes if an API is being used for automation script. Reports: Using API and a BI tool will provide immense power for generating business critical reports for an organization, where data can be extracted using API from multiple tools. Performance: REST provides superior performance. Uniform interface: Thus, faster learning curve and faster development.  

Q 7. What are the primary API components?

Ans: Following are the primary Physical Components:
  • Restful http/ https-based API end points.
  • Central repository to track and manage API calls.
  • Licensing engine to track and manage licenses efficiently.
Functional Components
  • Security: Token based Authentication using secured encryption technology.
  • Integration Configuration: Dynamically configure and deploy integration bridges.
  • Data Extraction: Extract data from central repository.
  • Tool Data Access: Direct access of the tool data using Kovair Restful API and adapter.

Q 8. How can enterprises avoid ripping and replacing their legacy systems or integrations?

Ans: Data for most of the legacy tools are in silos and if at all they are connected, it was done using point-to-point integrators. Kovair Omnibus USP is to preserve your investment and allow integration using ESB to other related systems and increase organizational productivity. Omnibus with Kovair Rest API will not recommend to ripe or replace the existing system but to integrate them using a bus to have a greater value of the investment.  

Q 9. What is the Kovair API gateway?

Ans: Kovair API gateway is a Restful endpoint hosted in web server. Kovair APIs has been designed to provide users with a clean and straightforward experience for integrating with Kovair ALM and Omnibus. Kovair APIs are RESTful in nature. REST stands for “Representational State Transfer”. Kovair API is a Restful API that adheres to the principles of REST and does not require the client to know anything about the structure of the API. It supports http, https, TLS 1.1 or TLS 1.2 encryption.  

Q 10. What is the Kovair API Value Proposition?

Ans: Following are the value propositions:
  • Extract Data from Platform: since Kovair platform is the central repository for Solutions like DevOps, Agile, Defect Management, etc.; thus organizations can extract raw data from the platform to their own best of breed tools for generating organizational specific reports.
  • Support IT teams to provision workspace and Omnibus configuration from their own tool.
  • Push data to platform from external resources to build a data repository.
  • Extract data from the connected tools directly using API, Platform, and Adapter. This feature is currently limited to supported tools only.
  • Extract omnibus transaction data from platform to build analytical tree in their BI / Reporting Tools.

Q 11. What can you tell our audience about leveraging the Kovair Omnibus Platform?

Ans: Kovair Omnibus is one of the flagship integration product based on ESB model. Currently, we have about 80 different third party tools for Integrated ALM and DevOps. Kovair has leveraged the same platform to expose Restful API as an end point to provide immense power to the end users.  

Q 12. Can the Kovair Platform be leveraged as a Central Repository?

Ans: Yes, Kovair Omnibus is one early solution providers from 2011 to provide an integrated solution using a central repository for traceability and dashboards.  

Q 13. Can you share a use case with the audience?

Ans: Yes, the IT team provisioning an integration bridges between tools externally for a business unit based on a request. The deployment can be done using easy scripting which can be deployed in minutes using Kovair API.  

Q 14. Would you like to add anything to our discussion before we wrap up for today?

Ans: Restful API is the heart of next-generation communication for Cloud and on-premises solutions.  

Q 15. Where can our audience get more information on the Kovair API?

Ans: On-premises / Cloud customers can enable API Access based on request. Source, Outlook Series – Kovair RESTful API Drives Fast Performance and Reliability