Hi All, In the process of supporting users to do micro-service transformation, we encountered the following problems: 1. For users who integrate multi-vendor applications, because the development languages, habits, and frameworks of different vendors are different, the entire system data and service standards are inconsistent, users are difficult to integrate, and it is difficult to manage and control the final delivery quality. 2. For users who have evolved from legacy systems to microservices architectures, additional learning and understanding of the microservices-related framework details is required before the microservices project can be designed, built, and developed according to the selected microservices framework. For users, Need to be distracted to focus on things outside the business.
Based on the above reasons, combined with ServiceComb's service contract management capabilities, we have implemented a contract-based microservice development toolkit[1] with the goal of rapidly building microservices projects based on popular microservices frameworks and programming models, and supporting the automatic generation of contracts,code and documentation to help users reduce micro-service entry costs, focus on business development, and improve legacy system reconfiguration and development efficiency during the microservice transformation phase. The framework and basic function of toolkit has been finished [1] The function of the toolkit is as follows: 1. Code extraction service contract In applications developed based on the SpringMVC/POJO/JAX-RS model, one-click generation of service contract files conforming to the OpenAPI specification. 2. Service Contract Generation Micro Service Engineering Enter a service contract that conforms to the OpenAPI specification, one-click generation of a microservice project with ServiceComb/SpringCloud/Swagger as the base microservice framework and SpringMVC/POJO/JAX-RS or SpringBoot as programming model . 3. Service contract and code consistency check Verify that the actual implementation of the application (such as the data and service API) is consistent with the agreed service contract description. 4. Service contract / code generation document Enter a service contract that conforms to the OpenAPI specification, one-click generation of a document in html/word/pdf format. [1] https://github.com/MabinGo/toolkit Best Wishes & Regards ------------------------------- Mabin