This content is permanently moving to https://www.apiopscycles.com and will not be available from this address after Dec 21th, 2018
The APIOps® Cycles is a set of tools and methods for designing API Management compatible API’s with Clear business orientation and best practice architecture patters.
APIOps® method uses modern and proven frameworks with a twist of our experience to the them for APIs. All methods have a Lean management base: DevOps (wikipedia), Business Model Canvas (wikipedia), Value Proposition Canvas, Lean Startup (wikipedia), Minimum Viable Architecture and API Model Canvas. Afore mentioned frameworks, tools and methods have been re-interpreted to create the APIOps® Cycles.
APIOps® Cycles is created in collaboration with open non-profit APIOps.net Community and Digia Plc. APIOps® is a registered trademark of APInf Oy. Templates and method is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License (CC BY-SA 4.0)
APIOPs® community is open for all and used as framework to promote and develop APIOps® Cycles.
RESTful API’s are in the core of services. One major difference to normal API development is that APIs are considered as products, not unique services. APIs are owned, improved continuosly and should be advocated for the consumers. They can be sold and bought and they are the lifeblood to the applications using them.
The APIs should provide not only value to your consumers but should be appealing to developers. They should be easy to understand, discover and use, a set of API’s should always be consistent. API’s can be used by several consumers; applications or even devices.
All methods used are technology agnostic. Used technology to create, manage, release and test the APIs should be evaluated per purpose. Open source technologies as well as commercial products are possible to use with APIOps® Cycles.
APIOps® goal is to design, build, test and release APIs more rapidly, frequently and reliably. In short, to build standardized API value chain automation
Digia Plc is using APIOps® Cycles in their own customer projects. The purpose of the guidelines is to define standards in API Driven development and to continuosly develop the methods and best practices.
APInf Oy contributes to APIOps® Cycles and promotes it to all customers. Although APIOps® trademark is registered trademark of APInf Oy, it stays with community, contributors and members are encouraged to address it. APIOps® trademark brings an unique identity to the community. APInf Oy commits to stay as active contributor and partner of APIOps®.