comicbookshop

Project Architecture

Welcome to the project architecture notes.

The primary purpose of the project is do the usual .net micro services approach which makes in the context. I have a basic e-commerce project going on here. The app is to do the following.

authentication and authorization service/api
basic e-commerce operations
1. product management service/api
  1. customer should be able to look at products
  2. admin should be able to add and edit products
2. order management service/api
  1. customer places orders
  2. admin manages it
3. coupon management service/api
  1. customer uses coupons during checkout
  2. admin manages coupons
4. shopping cart management service/api
  1. customer adds and removes products from the cart
message bus and email processor/logger
1. Collect messages from different services and put it in the Azure queue
2. Receive messages from the Azure Queue, and process it (like log the database to the database. in the future, may be, send email and such)
Provide a web app that gives a UI to do all the above
1. customer does customer things
2. admin does admin things

Now, each component is developed as a separate project, either as a web api, or a web app or a class project. That means, each of them can be individually developed, debugged and deployed. This leads to some duplication (like DTO classes for example), but, it’s a small price to pay for the flexibility offered by the micro service approach.

book a session with me

calendly

hire and get to know me

find ways to hire me, follow me and stay in touch with me.