I was giving a APIOps concept presentation at DevOps Finland meetup in Pasila. Eficode was hosting the event and the space was crowded with devops specialists. Without saying, it was clear that the audience was the best possible for pitching. Participants were experts and not holding back on feedback; it was hard and to the point!
One topic that raised discussion was how to include continuous integration to the APIOps process, which is Design driven. My answer was that I haven’t yet had time to think that over. For time being I have limited the feature scope to MVP just to get something done and clear. And yet, the concept is not clear but requires more pitching and modifications.
Another more interesting topic that came up in discussions with a few participants after the presentation was the scope of applying APIOps. I have been too focused on thinking APIOps through development of one API. The value comes when scope is bigger. DevOps principles and practices fit in the scope of one API.
Harmonizing API families between various partners.
One of the participants in this small group chatting was Toni Willberg from RedHat. It came as a lightning to me that APIOps is about building and harmonizing consistent API families or ecosystems.
APIOps is not about speed. APIOps is not about automation itself. That is what DevOps is about.
APIOps: With the help of using API descriptions and sandboxes generated from there, result functions as communication platform, which can be utilized to create harmonized multi-partner API ecosystems.
Harmonization cuts costs in integration and development, enables lower learning curve for the API consumers, creates stability and increases security, and enables automatization in large scale IoT systems.
API orchestration with Design-First approach
APIOps process starts with API design in collaboration with API consumers and other key partners. Using API description standards like RAML, Swagger and API Blueprint enables automatic generation of API sandbox and mockup server from API description at any point of the design process. In other words, it enables iteration and API (human) testing without manual coding. This process is done with each API. Then we will have group of APIs which can be tested to work together.
In other words we are talking about API orchestration, enabling seamless API networks.