/gunpla-store

Learning Event Driven Architecture with use case of Gunpla Store

Table of Contents

Gunpla Store

An E-Commerce for Gunpla lovers to buy and sell their Gunplas

Reason to build this project

I want to learn and try Event Driven Architecture microservice for keep up to date with startups needs

Stack

Currently i'm going to use GO as main language, with MongoDB as database, Apache Kafka for message broker, Docker for containerization, Docker Compose for container orchestration tool (i was thinking to use Kubernete or K3s for the orchestration tool), Datadog for distributed tracing tool, Mailhog for email testing purpose, Xendit for payment gateway

Summary

  • GO
  • MongoDB
  • Apache Kafka
  • Docker
  • Docker Compose
  • Datadog
  • Mailhog
  • Xendit

Footnote

At first i was thinking about using ELK (ElasticSearch, Logstash, Kibana) stack for the architecture, but i drop the idea

Services

  • Bff

Service Backend For Frontend (BFF) handle all requests from frontend to backend systems

  • User

User service for authorization and user details such as address, name, etc. And for seperate if the user is Customer or Seller

  • Inventory

This service would be responsible for managing the inventory of products in the system. It would maintain information about available stock levels, pricing, and product details

  • Product

Product service would handle the management of product information, including descriptions, images, and specifications. It would be responsible for updating the product catalog and making sure that product information is up-to-date and accurate

  • Order

This service would be responsible for managing the order process, including accepting and processing orders, tracking order status, and handling payment processing

  • Generic

Service for collecting data for other service needs

  • Mail

Service for sending emails to the customers; such as OrderCreated OrderSuccessetc

Diagrams

TO BE ANNOUNCE

Database

TO BE ANNOUNCE