architect

netaxe2023/05/30

foreword

The early platform was a single application. With the increasing function and demand, the cost and disadvantage of maintaining a single monolithic application gradually became prominent and reached an intolerable point.

Every minor feature update forced the entire back-end service to restart, causing a brief loss of front-end interaction.

The increase of development members, from the front and back end, tools, architecture of one person to more than one division of labor to perform their own duties, a variety of processes, norms, standardization problems have to be considered and solved.

Architecture design principle

From the perspective of architectural maintainability and standardization, each back-end application should have a relatively consistent code directory structure, consistent configuration load specification, and consistent message bus configuration.

All microservice applications should be easy to deploy, repeatable functional modules (repeatable, simplified deployment steps)

Generic API endpoints.

Technical architecture diagram

Back-end technology selection

Front-end technology selection

Last Updated 12/15/2023, 3:14:33 AM
公告
🎉🎉🎉 Netaxe The micro-service version will be released soon. After the release of the micro-service version, there will be no major updates, so you can try it as much as you like. We hope you can actively feedback your experience on wechat group, GitHub and Gitee。

Add wechat first... Then join the communication group...

Git仓库