How prem-kumar-e/orderflow works
This repository implements a small order-processing system: clients manage products and submit orders; order creation checks the product service, records an order, and publishes an event for asynchronous notification handling. The sampled code shows in-memory product and order state, an AWS SQS publisher, and an SQS-triggered Lambda handler. The README is empty, and deployment configuration is excluded; notification work beyond logging is a TODO.
Main entry points: OrderController.cs Order endpoints · ProductController.cs Product endpoints · ProductService/Program.cs Product API host · OrderService/Program.cs Order API host
Components 11
Product catalog
- Product API host
ProductService/Program.cs - Product endpoints
ProductService/Controllers/ProductController.cs - Product model
ProductService/Models/Product.cs
Order processing
- Order API host
OrderService/Program.cs - Order endpoints
OrderService/Controllers/OrderController.cs - Order model
OrderService/Models/Order.cs
Notifications
- Notification handler
NotificationService/Function.cs
Other components
- API client
- Product service
- Order events queue
- Lambda logger
Connections 11
- API client → Product API host: HTTP requests
- Product API host → Product endpoints: maps controllers
- Product endpoints → Product model: uses model
- API client → Order API host: HTTP requests
- Order API host → Order endpoints: maps controllers
- Order endpoints → Order model: creates order
- Order endpoints → Product service: checks product
- Product service → Product endpoints: HTTP lookup
- Order endpoints → Order events queue: publishes event
- Order events queue → Notification handler: invokes handler
- Notification handler → Lambda logger: logs event