How open-hand/choerodon works
Project type and purpose
• This is an open-source, full-stack microservices platform (Choerodon 2.0) for enterprise agile collaboration across the whole value chain.
• It provides a suite of Spring Cloud–based microservices (Eureka registry, gateway, authentication, IAM, file/message/monitoring services, DevOps toolchain integration, workflow engine, code+artifact repositories, cluster agent) plus a React/Ant-Design frontend.
File structure and README
• The repository itself contains documentation (README files, ROADMAP, screenshots, changelogs) and no service code.
• However, the README enumerates each microservice, its responsibilities, and external integrations (GitLab, Kubernetes, Istio, Knative, Nexus, Harbor, etc.).
README for architecture insights
• Component relationship list shows a Maven parent POM (“choerodon-parent”) with child modules for each microservice.
• All backend services use Spring Cloud, register to Eureka, and are routed through Spring Cloud Gateway.
• Key external dependencies: GitLab (code repo), Nexus/Harbor (artifact repo), Kubernetes clusters (deployment environments), message bus or DBs (persistence and events).
Detailed capture of essential elements
• Services under the “choerodon-parent” umbrella to show their common inheritance of dependencies.
• Cross-cutting services (choerodon-swagger for docs, choerodon-monitor for auditing).
• How choerodon-starters (core library) underpins all microservices, even though it’s not a runtime component.
• Cluster-agent’s dual role: connecting the platform to Kubernetes clusters for continuous delivery and environment management.