Why do we need API in software?


If you have ever worked in an environment where communication between departments flows openly and smoothly, then you know the efficiency of clear direction in objectives and strategies with top-down cross functional collaboration. The same professional values amidst a diversified workplace are clearly evident, and the result is a feeling of connectedness to a shared vision. You are able to find satisfaction in contributing to successes and reaching goals. However, without communication between departments and clear direction, everything and everyone quickly begin to experience friction. Any spark of initiative is quickly put out by relentless stagnation while small misunderstandings mount to large issues in workflow and productivity.


The same scenario might occur within a complex software product such as an operating system when components are not properly configured to communicate with one another. More specifically, these scenarios are the difference between an operating system with (or without) an effective abstract layer interface like Abaco’s AXIS Takyon API.

At Abaco, we have relied heavily on open standard API such as VITA 46.11, IPMI, and the SOSA technical standard. We have taken the time to innovate when interfaces weren’t readily available and analyzed the complex reality of addressing heterogeneous systems with multiple CPUs/GPUs/FPGAs. The result? A clearly defined and structured API across abstraction layers resulting in next level interoperability which allows for applications to communicate uniformly within the entire system.

The AXIS Takyon API brings measurable benefits into the developer’s hands to go above and beyond functionality so that interoperability is at the core of the client’s success. It offers availability for use as-is in different environments without major migration time to deployment with an intuitive platform for a low learning curve. This reduces time to deployment from months to just weeks. It also allows for minimal lines of code for single connection with full error checking in connected binding mode. AXIS Takyon API is designed for efficiency, flexibility and performance based on limited number of APIs, one-way/receive notifications binding and zero-copy transfer. Developers can use complex or low-level connectivity with an abstraction layer ready to support either end of the spectrum. Finally, the Takyon API introduces predictable, measurable and reproduceable perturbation in the Send/Receiving activity.

Utilizing an operating system enhanced with AXIS Takyon API that is fully functioning in a way that utilizes interoperable components to create a smooth flow of communication is truly a game changer. Abaco is ready to deliver the abstraction layer which lends itself to your success. And if you haven’t experienced a work environment with the same tendencies, I assure you they do exist. I am proud be a part of Abaco, where that incredible sense of purpose, direction, and smooth communication between departments is central to our company culture and functionality.


Francesco Fiaschi

Francesco is Abaco’s Software Product Manager. Having graduated from the University of Padova in Italy with a masters degree in electrical and electronics engineering, he has held a number of positions with a range of companies including Wind River, Intel, Infineon Technologies, Spirent Communications and Access Europe. He joined Abaco in July 2018.