Automation: Are We Looking at the Next Evolution of APIs?
The evolution of APIs ushered in a new era of communication between applications, systems, and services. Zdenek Nemec discusses this in Coding Over Cocktails.
Join the DZone community and get the full member experience.Join For Free
Editor’s note: This interview of Zdenek Nemec was recorded for Coding Over Cocktails - a podcast by TORO Cloud.
APIs are considered the cornerstone of any digital transformation project. Through APIs, organizations can securely expose data to internal systems, customers, and business partners. They can also be a path to new revenue opportunities by creating digital products out of an organization’s data or business processes.
Over the years, we’ve witnessed the evolution of APIs and how they’ve ushered in a new era of communication between applications, systems, and services. However, with this evolution came a fair share of challenges around API delivery, discovery, and consumption due to the rapidly growing demand for APIs.
“We historically know that automation and autonomy is actually the solution to complexity. When a lot of people are doing something manually, people start thinking about how to automate and how to give it autonomy. The number of APIs and the way we keep them together by hands is just not going to scale," says Zdenek Nemec, founder of Superface.AI during an episode of the Coding Over Cocktails podcast.
The goal of Superface is to transform how organizations connect digitally by empowering developers through API automation.
“So, there’s this urge for us to take it further—to start thinking about automation—so we can use our engineers to create a better world, rather than just working on the wires,” adds Nemec.
Culture Over Technology
One of the fundamental changes that Superface has applied is on description formats, splitting the business layer of what an API can do and the actual implementation, be it through GraphQL or REST. By separating the business layer from the functional, operational programmers will be able to easily identify the components of an API.
Another thing that developers can consider implementing is giving freedom to clients when creating contracts. Clients can opt to seal the deal on the business case level and entrust all the implementation side to the programmers. This will ease the process when clients decide to switch providers who will fulfill the same business case. Programmers can now freely decide how they will implement the API while the clients focus on the business case.
Nemec stresses, however, that automation in enterprises should be seen as more of a cultural change rather than a technical one.
“This automation, CI/CD, and DevOps approach take actually more change in culture or mindset in the company. We see that we cannot have developers manually connecting to APIs if we are going to really get to some ‘AI future.' The question is, will this particle implementation be the one we think it will?”
A New Future for Digital Transformation?
Changing the way companies approach API automation will be the first step of working towards achieving digital transformation efforts while striving to drive business value.
“I think we, as mankind, will get there—probably not in Superface, probably not in the next decade, but I think we can take it very far. That's for sure. We are learning in the process," Nemec says.
Learn how API automation can help streamline the management of APIs with Zdenek Nemec on Coding Over Cocktails—a podcast by TORO Cloud.
Published at DZone with permission of Abigail Lavarias. See the original article here.
Opinions expressed by DZone contributors are their own.