RepoPilot

What are the migration paths between them?

About lihengming/spring-boot-api-project-seed · 2 messages · last activity 8/15/2026

Question

What are the migration paths between them?

RepoPilot

Based on the repository data provided, I don't see direct migration paths documented between lihengming/spring-boot-api-project-seed and yunaiv/yudao-cloud. These are distinct projects with different architectures:

Key Differences:

lihengming/spring-boot-api-project-seed is a monolithic seed project designed for:

  • Single Spring Boot applications
  • MyBatis + universal Mapper plugin for simple CRUD operations
  • Code generation for Models, Mappers, Services, and Controllers [src/test/java/CodeGenerator.java]
  • Unified exception handling via ServiceException [src/main/java/com/company/project/configurer/WebMvcConfigurer.java:L64-L66]

yunaiv/yudao-cloud is a microservices architecture featuring:

  • Multiple services (system-server, infra-server) with RPC API prefixes [yudao-framework/yudao-common/src/main/java/cn/iocoder/yudao/framework/common/enums/RpcConstants.java:L10-L30]
  • Code generation infrastructure (infra_codegen_table) in the database schema
  • Multiple database platform support (PostgreSQL, HighGo, KingBase, OpenGauss, etc.)

Possible Manual Migration Approach:

If migrating from the seed project to yudao-cloud, you would need to:

  1. Restructure the monolith into services
  2. Replace MyBatis code generation with yudao-cloud's infrastructure-based approach
  3. Implement RPC/service-to-service communication using yudao-cloud's patterns

However, no automated or documented migration path exists between them in the provided repository data.

FOLLOW_UPS:

  • What is yudao-cloud's code generation architecture?
  • How does yudao-cloud handle service-to-service RPC communication?
  • What database platforms does spring-boot-api-project-seed support?

Public Q&A. Generated by RepoPilot from the actual source of lihengming/spring-boot-api-project-seed. AI answers can be incomplete or stale — verify before relying on them.