Introduction to vConnect

The vConnect module is a Vahana cloud incorporated web based portal. In the Vahana cloud platform, it works as a smart and scalable middleware that allows you to integrate the front-end application with the back-end service via the API call (Invocation) mechanism.

The vConnect module is based on the light-weight micro-service architecture. It allows you to perform the service orchestration by clubbing multiple API based functions into a single API point. The service orchestration enables the single point API to manage a client’s request and then return the response to the client via the multiple call-back mechanism.

Let’s understand the vConnect module as a middleware. A request is generated from the front-end application (Mobile app or web application). The front-end application sends the request to the vConnect integrated API. The API handles the incoming request, processes it, and then redirects it to the back-end/server. The API receives the response from the back-end/server and then returns the response to the front-end application.

vConnect Features

  • Single API based request and response mechanism to optimize data traffic and scale throughput
  • Allows monitoring, reporting and debugging to maintain overall API performance
  • Helps monetize the API efficiently
  • Allows incorporating patch and changes without affecting API performance and downtime
  • Incorporates web based dashboard to maximize the API performance by constantly monitoring and using other health metrics
  • Periodically captures the audio logs for reporting purposes
  • Having been based on the ELK stack, it provides the real-time server based machine monitoring experience.

What Will You Learn with vConnect

The vConnect module is a web-based middleware that has a wide functional scope. Based on the application-level requirements, you can configure APIs in multiple ways on the vConnect module. To configure an API, you will learn the followings:

  • API Management (Visit the topic: API Management with vConnect)
    • Configuring end-point URL from where the front-end application invokes the API
      • Configuring Path Parameters
      • Configuring Query Parameters (If required)
    • Configuring Header details (header parameters) (If required)
    • Configuring Request Body’s details (request body’s parameters)
  • Service Management (Visit the topic: Service Management with vConnect)
    • Creating a service and defining its details
    • Registering one or more APIs with the recently created service
    • Exporting the registered API as a service
Was this article helpful?