How ahmednaeim1/stylesphereapis works
Project type and purpose
• This is a backend-only microservices system (“styleSphereAPIs”) for a graduation project.
• It uses an API Gateway plus seven independent services, each handling a specific business domain (business, checkout, following, order, product, social, user).
File structure
• Root: contains an “apiGateway” folder (Node.js) and one folder per microservice.
• apiGateway:
• gateway.js orchestrates routing to downstream services
• routes/… and controllers/… mirror each service’s API endpoints.
• businessService: .NET Core service with Controllers, Models, Repositories, appsettings, launch configurations.
• checkoutSerrvice: Java Spring Boot (pom.xml, src/main/java with controllers, models, repository).
• followingService & orderService: Python Flask apps (app.py, controllers, models, repositories, swagger.json).
• productService, socialService, userService: Node.js/Express apps with api/controllers, api/routes, api/repositories, dbConfig.
• Each microservice likely has its own database (config files), models, and repository layer.
Detail without overthinking
• Every service, the gateway, and their databases.
• Client-to-gateway, gateway-to-service, service-to-DB, service-to-external/API flows.
• Do not omit any microservice or data store.