How phan-manh-dung/online-pc-store-be works
Project type and purpose
• This is a Node.js-based, microservices back-end for an “Online PC Store.” There is no monolithic UI here; instead, we have an API Gateway in front of multiple domain-specific services (cart, order, payment, product, search, recommend, user). Each service is Dockerized, uses Redis for caching, and exposes its own REST endpoints.
File structure
• Top-level:
• .github/workflows & Jenkinsfile → CI/CD pipelines (GitHub Actions + Jenkins)
• docker-compose.yml → local multi-container orchestration
• BackEnd/src/API_Gateway → single entry point for clients
• BackEnd/src/{cart,order,payment,product,search,recommend,user}_service → seven independent microservices
• Each service has: Dockerfile, controller/router/service/model layers, Redis client under redis/v1, middleware for authentication.
• Shared patterns: MVC-style within each service, Redis caching layer, environment configuration, Docker builds, package.json per service.
README
• README only gives the project name (“Online-PC-Store”), confirming an e-commerce system.
Detail without overthinking
• Every service as its own component.
• Data stores and caches alongside each service.
• CI/CD pipeline as an ancillary flow into your container registry / cluster.