In API design for microservices platform, deployment is the process of releasing a new version of an API to production. A mock release is a preparation phase for productive implementation. One goal of a mock release is to learn as many practical insights as possible while spending as little effort as possible. This can be achieved by quickly creating a simple prototype implementation, that you plan to throw away .
During the mock release phase, the critical aspects of the API are assessed. Assessment of the mock release is performed from a technical perspective by the engineers and from a usability perspective by pilot consumers. Typical design decisions that are explored during the mock release are the backend design decisions and the non-functional properties of the system .
The API mock release should conform to the API description and use real data from real backends. To achieve the necessary speed, the implementation does not have to be pretty, does not have to be optimized, and may contain engineering shortcuts. Code generation can be used to fulfill both goals of practical insights and low effort for the creation of the mock release. Properly generated code conforms to the API description. However, the generated code is merely the “bones” of a skeleton, only the interface of the API can be generated. The missing code can be added with relatively low effort since the skeleton already provides a structure .
When deploying an API, it is important to follow a deployment strategy that meets your business goals. There are several deployment strategies to choose from, including recreate deployment pattern, rolling update deployment pattern, and blue/green deployment pattern.