How cardano-foundation/originate works
Project type and purpose
• Originate is a full-stack, modular, traceability platform.
• A Spring Boot REST API (“api” module) for business workflows and off-chain storage in PostgreSQL.
• A React single-page dashboard (“frontend”).
• An Ionic/Capacitor mobile app (“mobileapp”).
• A suite of Metabus microservices for packaging, batching, submitting, and watching Cardano transactions.
• Supporting infrastructure (Kafka, RabbitMQ, MinIO, Keycloak, Cardano node).
File structure
• Top-level folders:
• api/ – Spring Boot service with controllers, business, repository, RabbitMQ consumer, Flyway migrations.
• frontend/ – React + Material UI dashboard.
• mobileapp/ – Ionic/Capacitor PWA and native mobile.
• metabus/ – subfolders for:
– cardano-metabus-api (ingestion REST + Kafka producer)
– cardano-metabus-jobproducer (batching, on-chain job creation via Kafka)
– cardano-metabus-offchain-storage (MinIO object store)
– cardano-metabus-txsubmitter (Kafka consumer → build & submit Tx to Cardano node)
– cardano-metabus-txwatcher (watch chain confirmations → RabbitMQ)
• config/, docker-compose*.yml, .env.*, Keycloak and RabbitMQ setup scripts, Makefile, Maven wrapper.
README for additional insights
• Confirms role-based API, PostgreSQL off-chain, push jobs to Metabus, which:
1. Enqueues on Kafka
2. Stores JSON in object storage
3. Picks UTXO, builds & submits metadata Tx
4. Watches confirmation, returns result via RabbitMQ.