How bahmn/rocket-factory works
This repository is a Go microservices system for order fulfillment: users create and manage orders, with identity, inventory and payment services supporting the order service; Kafka consumers handle paid/assembled events, and notification and assembly services provide downstream work. The graph separates synchronous APIs, persistence/integrations, and event-driven services. Some service internals and DI wiring were not excerpted; uncertain runtime links are dashed rather than asserted as inspected calls.
Main entry points: app.go Order API runtime · order Order operations · order_consumer Paid-order consumer · order_paid_consumer Paid-order handler
Components 25
Orders
- Order API runtime
order/internal/app/app.go - Order HTTP endpoints
order/internal/api/order/v1 - Order operations
order/internal/service/order - Order repository
order/internal/repository/order - Inventory client
order/internal/client/grpc/inventory/v1 - Payment client
order/internal/client/grpc/payment/v1 - Order event producer
order/internal/service/producer/order_producer
Identity
- Auth and user APIs
iam/internal/api - Identity services
iam/internal/service - Identity repositories
iam/internal/repository
Fulfillment
- Inventory gRPC API
inventory/internal/api/inventory/v1 - Inventory services
inventory/internal/service/inventory - Inventory repository
inventory/internal/repository/part - Payment gRPC API
payment/internal/api/payment/v1 - Payment service
payment/internal/service/payment
Event services
- Paid-order consumer
assembly/internal/service/consumer/order_consumer - Assembly event producer
assembly/internal/service/producer/order_producer - Paid-order handler
notification/internal/service/consumer/order_paid_consumer - Assembled handler
notification/internal/service/consumer/order_assembled_consumer - Telegram delivery
notification/internal/service/telegram
Shared platform
- Shared API contracts
shared/proto - Kafka runtime
platform/pkg/kafka
Other components
- Order user
- Kafka
- Telegram API
Connections 28
- Order user → Order API runtime: sends requests
order/internal/app/app.go - Order API runtime → Order HTTP endpoints: routes HTTP
- Order API runtime → Order event producer: starts consumer
order/internal/app/app.go - Order HTTP endpoints → Order operations: dispatches
- Order operations → Order repository: reads and writes
- Order operations → Inventory client: requests parts
- Order operations → Payment client: requests payment
- Order operations → Order event producer: publishes events
- Order API runtime → Shared API contracts: serves generated API
order/internal/app/app.go - Auth and user APIs → Identity services: dispatches
- Identity services → Identity repositories: uses repositories
iam/internal/service/auth/service.go - Order API runtime → Auth and user APIs: authenticates requests
- Inventory client → Inventory gRPC API: calls gRPC
- Inventory gRPC API → Inventory services: dispatches
- Inventory services → Inventory repository: reads parts
- Payment client → Payment gRPC API: calls gRPC
- Payment gRPC API → Payment service: dispatches
- Kafka → Paid-order consumer: delivers paid events
- Paid-order consumer → Assembly event producer: emits assembly events
- Assembly event producer → Kafka: publishes
- Kafka → Paid-order handler: delivers paid events
- Kafka → Assembled handler: delivers assembled events
- Paid-order handler → Telegram delivery: notifies
- Assembled handler → Telegram delivery: notifies
- Telegram delivery → Telegram API: sends messages
- Paid-order consumer → Kafka runtime: consumes through
assembly/internal/service/consumer/order_consumer/handler.go - Paid-order handler → Kafka runtime: consumes through
notification/internal/service/consumer/order_paid_consumer/handler.go - Assembled handler → Kafka runtime: consumes through
notification/internal/service/consumer/order_assembled_consumer/handler.go