How orbit-alliance/orbit-backend works
Project type and purpose
• It exposes an HTTP API for “user” operations (e.g., transferring coins) and has infrastructure adapters for a database (MongoDB) and a Web3 provider (blockchain node).
File structure
• Top-level files: go.mod/go.sum define dependencies; RFC01-Architecture likely contains design notes.
• internal/domain: core business objects (User entity, Commands, Events, Repository interface, shared types like MongoID).
• internal/application: “use case” or “service” layer—application logic (e.g., TransferCoins service).
• internal/infra: concrete adapters—db (Mongo) and web3 (blockchain) implementations.
• internal/interface: entry-points or “driving adapters”: HTTP controllers/routes and Web3 interface stubs.
Key insights from the README
• Project is a backend service that manages user accounts and coin transfers, integrating with a database and blockchain via Web3.