Q 1. Akshay, what are the key benefits of using API’s and Software Bus Middleware in general?
Thanks for the question…Michael.
An API is an application program interface (API) that allows for easier integration to tools and applications. Here, an application can “invoke” the 3rd-party application, allowing for better, more holistic, integrated solutions to occur. This can extend the life of existing applications, can allow for increased productivity in re-using existing modules, allow for newer “mash-ups” of hyper-converged solutions and services to occur, perhaps with better workflow decisions being automated, perhaps better metrics in dashboards, while Enterprise Service Bus (ESB) solutions from vendors allow for pre-built, pre-tested integrations to 3rd-party systems without having the need for knowing individual tool APIs and having a vendor manage any API updates. This leads to more seamless integrations, increased productivity and better operational efficiencies to occur.
Q 2. When it comes to API teams, when should Centralized, Decentralized and or Hybrid organizational structures be leveraged?
Good Question, Michael, as Enterprises move their silo’ed IT or fixed product solutions towards the cloud, and open their platforms to make it as a Service, API Team Best Practices include the creation of an API Product Manager & the API Architect, to be a centralized function with goals of turning IT from a Cost Center to a Value Center. An example is Cisco Systems turning their Unified Communications and VoIP products like PBXs, and Session Border Controllers to become virtualized as a service in Webex. While these team functions can be decentralized, it would then make sense to have cross-functional matrix reporting within distributed teams to ensure common APIs, tools, Enterprise Service Bus solutions, and common analytics and dashboards are leveraged. Otherwise we end up with disparate silo’ed solutions again.
Q 3. API monetization is often key to digital transformation. So, how can firms increase revenue with their API program? What are some of the different API Business Models?
Michael, as Enterprises transform with Digital Transformation, many are looking to transition their IT from a Cost Center to a Value Center, with newer business models. Enterprises can charge their customers using their APIs in different ways, charge per transaction, charge by a subscription model, charge API access to their platform as an upsell as what Salesforce does, charge based on revenues generated in rev-share approaches, or perhaps not charge at all but collect analytics proving increased sales have occurred from the seamless integration, or decreased costs from operational efficiencies gained.
Q 4. Akshay, what are the key benefits of Kovair’s Omnibus?
Thanks for the question…Michael
Kovair’s Omnibus is a proprietary Enterprise Service Bus offering with both synchronous and asynchronous data transfer between applications and tools: sync’ing for real-time updates between apps and tools like a “handshake” where all data between apps and tools are “in sync”, while asynchronous updates is more like an interrupt of data or a “jab”, to continue the analogy. Asynchronous syncing typically applies to Desktop based tools which when activated get synced with Omnibus and connected tools.
But Kovair’s Omnibus also has many other benefits, including:
- Best of Breed solutions integration, with over 90+ pre-built adapters which are pre-integrated to the applications. Some of the popular once are IBM’s Tools, ServiceNow, SAP, Cisco’s AppDynamics, CRM tools like Salesforce, and much more.
- Omnibus can be a Hybrid Cloud Enabler! Megaplex cloud, on-prem, to newer 5G Edge Clouds… all interconnected via Kovair’s Omnibus.
- Omnibus allows for Concurrent Multi-modal IT as we discussed last time, Michael, legacy ALM (applications lifecycle management) solutions can be “inter-connected” with DevOps Cloud-based services, and vice versa, all securely connected, with an added benefit of DRaaS, Disaster Recovery as a Service, as Omnibus allows for re-sync’ing if a server or server farm fails, with zero-loss of data using hitless synchronization between tools.
- And additionally, Kovair’s Omnibus with full support for Configuration-based API specifications without Coding is of immense power. Organizations can have multi-fold benefits, using Kovair’s Restful API Middleware solutions.
Q 5. On that note, Akshay, What are the key benefits of Kovair’s Restful API Middleware solutions?
- Kovair’s Omnibus platform offers the perfect blend of ESB and API flexibility with the capability to address complex use cases.
- Typical integration vendors are either an ESB Bus platform or an API middleware platform but not both.
- Kovair’s Restful API Middleware solution leverages its leading Omnibus solution and enhances it with automated configuration support.
- Kovair allows for automatic provisioning of Omnibus Integration externally using their API. Here, users would raise Integration requests in a provisioning platform that an API Services team could facilitate. Users can use this platform to review, approve, and finally initiate the Kovair Autoconfiguration solution by invoking the Kovair Omnibus API middleware platform. Organizations need to integrate their provisioning tool with Omnibus only once using a Restful API, and additionally using Kovair’s templates, re-use can occur.This will:
- Improve Reusability – Kovair’s Omnibus API can be used to auto-configure all the business mappings by providing a configuration template that can be reused over and over again to establish integration between tools and applications.
- Abstraction and easier migration to newer tools and Applications: Legacy hard-coded solutions to 3rd-party systems lock enterprises into sub-optimal solutions. Kovair allows for easier migration to newer best-of-breed solutions. Using Kovair’s platform, we can Extract the Integration data – with Kovair’s Automation API. Here, we can extract various transaction and configuration-related data for transfer to newer solutions. With the Kovair Data Lake with its analytics capabilities and syncing capability, these can be leveraged for disaster recovery as a service.
- Another benefit: is Visibility of the Configuration Setup – External applications can call the API to see the status of the integration configuration until the setup has been completed. This increases the visibility of the process.
- Security: because inter-application delivery of services and information is often required to be secure and Kovair’s Restful API platform allows for secure interfaces, this is a critical requirement nowadays.
All this should enable a better collaborative environment for better quality, better productivity, better security, and support for better operational resiliency.
Q 6. Thanks, Akshay, to wrap-up, what are the implications to business leaders for Kovair’s Omnibus and Restful API announcement recently?
There are many siloed solutions: some with software busses, some with data lakes and data migration solutions, some with API middleware pre-packaged with configuration capabilities, some with siloed ALM (applications lifecycle management) tools support, some with DevOps tools support to migrate to Cloud applications, some with dashboard and analytics data lakes and repositories, but only Kovair packages all of the above within one framework, with workflow automation functions, as well as project lifecycle management functions, for not only Technical Leaders but Business Leaders as well.
Q 7. Thanks, Akshay, Any final thoughts? Where can our audience get more information on Improving Business Models with Kovair REST API?
Thanks Michael, www.kovair.com
has a wealth of information there.
One final thought, I would highlight from this recent announcement is the notion of Configuration-based development, also known as Low-Code Development. Gartner has predicted recently that by 2024, low-code application development will be responsible for more than 65% of all application development activity. I believe Kovair is the only Low Code Applications Development Platform vendor that supports Low Code, Configuration-based RESTful API solutions with a Workflow Editor, a Database Migration tool, as well as an Enterprise software bus solution with connectors to 90+ apps, along with PLM project lifecycle management, ALM: applications lifecycle management, and DevOps support.
So hopefully this is a Game-changer !
Source, Outlook Series – Improving Business Models with Kovair REST API