RepoPilot

What are the migration paths between them?

About thinkaurelius/titan · 2 messages · last activity 8/15/2026

Question

What are the migration paths between them?

RepoPilot

I need to clarify: thinkaurelius/titan and yunaiv/yudao-cloud are two entirely separate projects with no migration paths between them.

thinkaurelius/titan is a distributed graph database written primarily in Java, designed for storing and querying large graphs with billions of vertices and edges.

yunaiv/yudao-cloud is a cloud-based application platform (based on the repository data showing Flowable workflow engine patches and database support for DM Database via Liquibase).

These are fundamentally different software systems:

  • Titan focuses on graph storage and traversal
  • yudao-cloud appears to be a business application platform with workflow and database abstraction layers

There is no direct migration path or architectural relationship between them. If you're asking about:

  1. Migrating data from Titan to yudao-cloud — that would require custom ETL logic, as they have incompatible data models
  2. Using Titan as a backend within yudao-cloud — yudao-cloud's repository data shows it uses traditional relational databases (Oracle, DM Database, PostgreSQL, etc.) via Liquibase and Flowable, not graph stores
  3. Something else — please clarify what you mean by "migration paths"

Could you provide more context about what you're trying to achieve?

FOLLOW_UPS:

  • Does yudao-cloud support graph database backends?
  • What is the primary use case for yudao-cloud?
  • Are you looking to integrate these systems?

Want to ask your own question?

Open chat for thinkaurelius/titan

Public Q&A. Generated by RepoPilot from the actual source of thinkaurelius/titan. AI answers can be incomplete or stale — verify before relying on them.