The platform interface construction specification aims to delimit a framework boundary for interface development, testing and use, define technical objectives and requirements, and provide complete interface documentation to provide data and service support for self owned platforms and third-party platforms.

It is observed that most platforms cannot fully follow this specification in interface design. My suggestion here is that both interface naming and parameter naming must be reasonably designed based on business and understanding needs to ensure simplicity, pragmatism and ease of understanding.

Idempotency means that the execution result of any multiple requests has the same impact as the execution result of one request. No matter how many times you query, the query operation will not affect the data itself, so the query operation itself is idempotent. However, the database will change every time the new operation is executed, so it is non idempotent.