Published on 11/18/2021
Are you preparing for an upcoming demo and some of the software components on the flow of execution aren’t ready yet?
You have two choices:
This is not an uncommon situation to be in and with the adoption of the microservices architecture, applications are increasingly being built as a collection of lightweight services or micro-applications. Microservices communicate with each other either via HTTP Request/Response Model or via Asynchronous Messaging Systems.
Let’s say that there is an Application that is made up of 10 microservices. Let’s assume that
If new features are being built into microservices 7–10, how would the developers working on those microservices demonstrate their new features to their teams, leadership, users and customers?
Dependencies, such as the one described above, between development teams can be solved by API mocking (or API Virtualization), to some extent.
API mocking can also help in scenarios where one or more APIs in the path of execution are unstable or unavailable and the teams responsible for maintaining them are unreachable. Mock APIs could be created in minutes to fill-in for the unavailable/unstable APIs in the path of execution.
API mocking can not only help during development and testing, but it could also serve as a valuable tool for smoother product demonstrations.