-
Notifications
You must be signed in to change notification settings - Fork 1
VII. Future Ideas
Currently the products only have a name, a description, key value information and a price. It would be nice to have more information about the products.
These further information's a could be:
- Product Category
- Product Tags
- Product Brand
- Product Variants (e.g. different sizes, colors, etc.) bound to a single product
Currently there is no way to upload images to the server. This feature could be interesting for the shop frontend UI. The Admin user will need to upload images to the server and then store the path to the image in the database.
A rough idea for the implementation could be:
- Create a new service called
image-service
- Service has a REST API to upload and download images
- Service has a cloud storage (like AWS S3, Google Cloud Storage, etc.) to store the images
- Service has a database to store the path and other information of the images
Currently the revenue is calculated in the order-service
. This is not perfect because the order-service
should only be responsible for the order.
A good solution could be to have a new service which is responsible for the revenue calculation. Further it could
also calculate profits if we start tracking the costs and purchases of the products. This service could
simply listen to the events of the order-service
and track the revenue.
A service that is responsible for the offerings of the shop, could give the admin user more control about what product is offered.
Currently every product is automatically offered in the shop, if it has stock. With an offering-service
this could change. Even
if a product is in stock it does not need to be offered. With this feature it would also be easier to offer for different markets.
Also the admin user could offer products for a limited time.