![]() It also helps to modernize the existing parts of your information system. Using an integration framework should be a key part of your APIs' lifecycle to promote reuse, fast iterations, and value additions through orchestration. Then, in the Implement phase, the actual API is developed using either an integration framework such as Red Hat Fuse or using the development language of your choice. That’s not something you can formally model in an API contract, but it will instead be reflected in your mocks and your tests. If you are a retail company, you will have to return an error if someone under 21 tries to buy alcohol. Here's an example that will highlight the importance of the Mock and Test phases. This will help refine the business expectations about your APIs share them between developers, testers, and business customers and later ensure your APIs conform to those expectations. In an acceptance test-driven development approach, you will have to define your test cases, based on examples, before implementing your APIs. You could also think about mutually exclusive options or dependencies between fields: for example, if the field companyName is set, then the field accountType needs to be “enterprise.” An example could be that when querying items by status, all returned items must have the desired status. "Business expectations" entail everything that cannot be specified using a formal schema. Those examples are then turned into a live mock that can be exposed to your first consumers. In the Mock phase, you will define meaningful payload examples of your APIs and try to refine your specifications with business expectations for common and edge cases. In the Design phase, you design the contract of your API and share it with your future consumers. The outcome of the Design phase is an API contract that describes the messages that can be exchanged with your APIs. Also, a contract-first approach is known to reduce the time to market. This phase entails gathering feedback early, breaking the dependencies between projects, and reducing risks. The Design phase will ensure your organization uses a contract-first approach. This is a critical step to help you put effort where it matters the most. It also specifies which markets you need to address, which resources you have at your disposal, the time frame you have in which to achieve your goals, and so on. The leftmost cycle covers the producer activities, while the rightmost cycle covers the consumer activities.Īny API program has to start with a Strategy phase where you will have to define the goals you want to achieve with your APIs. This article describes a set of full API lifecycle management activities that can guide you from an idea to the realization, from the inception of an API program up to management at scale throughout your whole company.Īs shown below, the API lifecycle is two-fold. The success of your digital transformation project depends on it! With APIs becoming so central, it becomes essential to deal with full API lifecycle management. Salesforce generates 50% of its revenue through APIs, Expedia generates 90% of its, and eBay generates 60% of its. And those APIs are a key driver for generating new revenue. All those technologies expose, consume, and are built on APIs. APIs are the cornerstone of so many recent breakthroughs: from mobile applications, to the Internet of Things, to cloud computing.
0 Comments
Leave a Reply. |