Concurrent development with Mesh Dynamics

Updated 3 months ago by Rahul Lahiri

Mesh Dynamics enables concurrent development of APIs with dependencies, as well as parallel development of the application front-end and the back-end APIs the front-end depends on. Mesh Dynamics enables this capability by providing multiple easy-to-use options for creating API mocks, and a flexible request matching capability that can be either strict or relaxed.

This section assumes familiarity with the API Studio. If you are new to API Studio, please refer to the getting started documentation to get familiar with the basics of API Studio.

Creating API mocks

Whether developing APIs with dependencies or developing front-end in parallel with the back-end, the first step is to create mocks for the required APIs. Mesh Dynamics provides a rich toolset to make the process of creating API mocks efficient.

The two common configurations supported by Mesh Dynamics are:

Front-end development

When the front-end and back-end teams need to develop in parallel, the back-end developers can create mocks for the APIs the front-end team needs, but are not yet available for the front-end team.

API development with dependencies

For microservices development, it is common for different teams to be responsible for different services. Often there are dependencies among the services. When both the consumer API and the provider service are being developed in parallel, and the provider APIs are not yet available, the provider API developers can create mocks for the APIs the consumer API developers. This collaboration is easy to support with Mesh Dynamics.

Options for creating API mocks

There are three options for creating the API mocks.

  • From service in IDE: If the APIs are available locally in an IDE on the developer’s machine, then we can capture API request and responses locally using API Studio.
  • From API in dev cluster: If the APIs are available in a dev cluster, then we can capture examples from the live services using API Studio.
  • Manual mock creation: If the APIs are not available, then the mocks can be created by hand in the API Studio.

You can use any combination of the sources above to create a collection of API mocks.

While the overall process of how you consume the mocks is similar regardless of how you create the mocks, the details vary depending on how the mocks are created. We also outline the process of addressing the differences, and converging the API mocks to a uniform format regardless of how they are created. Please go over the following sections and get familiar with the differences between the three options.

Before going into the mock creation process, let us go over how Mesh Dynamics translates between service name / API path and the request URLs, and the differences between capturing request URLs vs creating the request URL for mocks in API Studio. Learn more.

How did we do?