• Create API Description
• Select API Template
• Launch Mock On Mock Server
• The goal is to provide a prototype
• Feedback from stakeholders
   

When designing a microservices platform, it is important to keep in mind the following five design principles :

Single Responsibility Principle: Each microservice should have a single responsibility.
Loose Coupling: Microservices should be loosely coupled.
Autonomous: Microservices should be autonomous.
Domain-Driven Design: Microservices should be designed around specific business domains.
Resilience: Microservices should be designed to be resilient.

Here are some additional details about each principle:
1. Single Responsibility Principle: Each microservice should have a single responsibility. This means that each microservice should be responsible for one thing and one thing only. This makes it easier to maintain and update the microservice, as well as making it easier to test.
2. Loose Coupling: Microservices should be loosely coupled. This means that each microservice should be independent of the others, and should not rely on any other microservice to function. This makes it easier to scale the microservices, as well as making it easier to update them.
3. Autonomous: Microservices should be autonomous. This means that each microservice should be able to function independently of any other microservice. This makes it easier to deploy the microservices, as well as making it easier to test them.
4. Domain-Driven Design: Microservices should be designed around specific business domains. This means that each microservice should be designed to handle a specific business function. This makes it easier to understand the microservices, as well as making it easier to maintain them.
5. Resilience: Microservices should be designed to be resilient. This means that each microservice should be able to handle failures and errors gracefully. This makes it easier to recover from failures, as well as making it easier to maintain the microservices.

In addition, when designing APIs for microservices, it is important to keep in mind that all data exchange between services happens either through messages or API calls. APIs must be efficient to avoid creating chatty I/O. Because services are designed by teams working independently, APIs must have well-defined semantics and versioning schemes, so that updates don't break other services.