anami283/legacy-demo-erp

Purpose and runtime

Legacy ERP is an internal Java application for sales, inventory, and billing. It is packaged with Maven and containerized for local deployment via Docker Compose. The executable application entry point is src/main/java/com/northstar/erp/LegacyErpApplication.java; deployment artifacts are Dockerfile and docker-compose.yml.

Application boundary

The web-facing sales boundary is src/main/java/com/northstar/erp/web/SalesController.java. It accepts sales-oriented requests and delegates business work to domain services rather than directly managing storage. The README identifies a default admin/admin user, implying authentication is part of the deployed application or container configuration, though no auth source appears in the tree.

Sales-order domain

Order creation and lifecycle are centered on src/main/java/com/northstar/erp/orders/OrderService.java, with aggregate/request structures in:

• src/main/java/com/northstar/erp/orders/SalesOrder.java

• src/main/java/com/northstar/erp/orders/SalesOrderRequest.java

• src/main/java/com/northstar/erp/orders/OrderLine.java

Orders are persisted behind src/main/java/com/northstar/erp/orders/OrderRepository.java, currently implemented by src/main/java/com/northstar/erp/orders/InMemoryOrderRepository.java. This interface/implementation split is the main persistence replacement boundary.

Customer and inventory dependencies

Sales processing depends on customer lookup/management through src/main/java/com/northstar/erp/customers/CustomerService.java and src/main/java/com/northstar/erp/customers/CustomerRepository.java. Inventory availability and stock operations are owned by src/main/java/com/northstar/erp/inventory/InventoryService.java, backed by src/main/java/com/northstar/erp/inventory/InventoryRepository.java; products are represented by src/main/java/com/northstar/erp/inventory/Product.java.

The in-memory implementations (InMemoryCustomerRepository.java, InMemoryInventoryRepository.java) indicate process-local, non-durable state rather than an external database.

Billing and payment flow

Invoice generation/handling is isolated in src/main/java/com/northstar/erp/invoices/InvoiceProcessor.java, using Invoice.java and the InvoiceRepository abstraction. Payments are represented and processed separately by:

• src/main/java/com/northstar/erp/payments/Payment.java

• src/main/java/com/northstar/erp/payments/PaymentService.java

The likely control flow is sales request → order service → customer/inventory validation and stock changes → order persistence → invoice processing → payment handling. Invoice and payment concerns are distinct boundaries, enabling later integration with durable billing or payment services.

Shared domain contract

src/main/java/com/northstar/erp/shared/Money.java is the cross-domain monetary value type. Orders, invoices, and payments should exchange monetary amounts through this shared model rather than primitive numeric values, making it a key consistency boundary.

Infrastructure and extension points

No database, message broker, payment gateway, or other external service is visible in the repository tree. Runtime infrastructure is Docker/Docker Compose; persistence is presently in-memory. The repository interfaces in customers, inventory, orders, and invoices are the principal seams for introducing durable storage without changing service-level workflows.