How huyhieu19/carsties_car_auction works
Project type and purpose
• This is a full-stack, microservices-based auction/web-app learning project.
• Frontend: Next.js (React) web application.
• Backend: .NET Core microservices (AuctionService, BiddingService, NotificationService, SearchService, IdentityService, GatewayService) communicating via RabbitMQ and gRPC.
• Purpose: Learn end-to-end microservices, event-driven communication, auth (IdentityServer), real-time updates (SignalR), search, Docker/Kubernetes.
File structure
• Top-level:
• fontend/web-app – Next.js app with pages, API routes (NextAuth), components, styling, fetch wrapper.
• src – multiple .NET Core services, each in its own folder with Dockerfile, csproj, Program.cs, controllers, services, data, migrations, protos (for gRPC), consumers (RabbitMQ).
• src/Contracts – shared event contracts (AuctionCreated, BidPlaced…).
• docker-compose.yml – orchestration of all services and RabbitMQ.
• Patterns:
• API Gateway (GatewayService) fronts all microservices.
• IdentityServer (IdentityService) for authentication/authorization.
• Event-driven communication via RabbitMQ: services publish domain events, other services consume.
• gRPC between BiddingService and AuctionService for direct auction lookups.
• SignalR hub (NotificationService) to push real-time notifications to frontend.
README insights
• Describes Docker Compose for running backend, Next.js for frontend.
• Mentions key technologies: .NET Core, EF Core, SignalR, RabbitMQ, Kubernetes, NextJS.
Final advice
• Be exhaustive: break out each microservice and its DB, show the Contracts library as a shared component.
• Token flow: client obtains JWT from IdentityService, includes it in calls to GatewayService.
• RabbitMQ at the center of the event-driven part.
• Don’t over-aggregate: treat each background consumer as part of its parent service.