How jojo165556/cryptotracker-lab works
CryptoTracker Lab is a teaching-oriented modular Django crypto-trading application. A user interacts through the dashboard or an API; trading use cases create and execute orders, with wallet balances and positions updated through repositories. Separate modules provide identity, market data, analytics, notifications, and payment settlement. The README documents REST, GraphQL, WebSocket, SSE, gRPC, JSON-RPC, webhooks, and SOAP capabilities. Edges from sampled code are cited to their callers; protocol coverage and unsampled interface wiring rely on README statements, so some links remain unverified.
Main entry points: use_cases.py Trading use cases · infrastructure/repositories.py Order repository · infrastructure/repositories.py Wallet repositories · app.js Dashboard
Components 26
Client interfaces
- Dashboard
frontend/static/js/app.js - REST APIs
trading/interfaces/api.py - GraphQL API
core/graphql_api/schema.py - gRPC Order Engine
order_engine/server.py - Analytics JSON-RPC
analytics/interfaces/api.py - Legacy SOAP
legacy_bank/interfaces/soap_service.py - Market WebSocket
market/interfaces/consumers/price_consumer.py - Notification SSE
notification/interfaces/sse.py - Payment Webhook
payment/interfaces/views.py
Trading domain
- Trading use cases
trading/application/use_cases.py - Orders and trades
trading/domain/entities.py - Order repository
trading/infrastructure/repositories.py - Market service
market/application/use_cases.py
Wallet and payments
- Wallet use cases
wallet/application/use_cases.py - Wallet and ledger
wallet/domain/entities.py - Wallet repositories
wallet/infrastructure/repositories.py - Payment settlement
payment/application/use_cases.py - Payment task
payment/interfaces/tasks.py
Product services
- Identity and security
identity/infrastructure/auth.py - Analytics service
analytics/service.py - Notifications
notification/application/use_cases.py - Legacy bank service
legacy_bank/application/use_cases.py
Runtime platform
- GraphQL loaders
core/graphql_api/dataloaders.py - Relational database
- Redis Pub/Sub
Other components
- User
Connections 27
- User → Dashboard: uses
- Dashboard → REST APIs: API requests
- Dashboard → GraphQL API: queries
- Dashboard → Market WebSocket: live updates
- REST APIs → Trading use cases: dispatches
- Trading use cases → Order repository: reads and writes
trading/application/use_cases.py - Trading use cases → Orders and trades: creates and executes
trading/application/use_cases.py - Trading use cases → Wallet repositories: loads wallet
trading/application/use_cases.py - Trading use cases → Wallet and ledger: updates positions
trading/application/use_cases.py - gRPC Order Engine → Trading use cases: invokes
order_engine/server.py - gRPC Order Engine → Order repository: reads orders
order_engine/server.py - Wallet use cases → Wallet repositories: persists
wallet/application/use_cases.py - Wallet use cases → Wallet and ledger: applies rules
wallet/application/use_cases.py - Payment Webhook → Payment task: queues settlement
- Payment task → Payment settlement: invokes
payment/interfaces/tasks.py - Payment task → Wallet use cases: credits wallet
payment/interfaces/tasks.py - Payment settlement → Wallet repositories: settles payment
payment/application/use_cases.py - Analytics JSON-RPC → Analytics service: dispatches
- Analytics service → Order repository: queries orders
analytics/service.py - Analytics service → Wallet repositories: queries wallet
analytics/service.py - GraphQL API → GraphQL loaders: uses loaders
- GraphQL loaders → Order repository: loads market data
core/graphql_api/dataloaders.py - Market WebSocket → Redis Pub/Sub: publishes updates
- Notification SSE → Notifications: streams notifications
- Legacy SOAP → Legacy bank service: dispatches operations
legacy_bank/interfaces/soap_service.py - Order repository → Relational database: persists orders
- Wallet repositories → Relational database: persists wallets