How burakkontas/discordclone works
Project type and purpose
• This is a microservices‐based backend for a Discord‐style chat application.
• It employs a star topology: a single CentralService mediates all external REST calls and routes internal RPCs to specialized services (Auth, Message, Email).
• Each microservice follows a layered architecture (Application, Service, Domain, DataAccess, Infrastructure) and communicates via gRPC internally.
File structure
• Top-level directories per microservice (e.g., AuthService.Application, AuthService.Service, AuthService.DataAccess, AuthService.Domain, AuthService.Infrastructure) reveal a clear layering:
• Application: Controllers, Handlers, Queries (MediatR patterns)
• Service: business logic implementations and adapters
• Domain: core models and protobuf definitions
• DataAccess: repository interfaces and implementations
• Infrastructure: database contexts and SQL scripts
• Discord.AppHost is the host project that wires all services together (builds and runs them).
• Configuration files (appsettings.json, launchSettings.json) are present in each Application project.
• Protobuf files in Domain/Protos define gRPC contracts.
README for additional insights
• Confirms star topology, gRPC for inter‐service comms, REST on CentralService.
• Lists REST endpoints exposed by CentralService for messages, auth, email.
• Mentions Elasticsearch for MessageService storage and general .NET Core 8 technology stack.
Detail
• Service’s datastore connection.
• Protocols (HTTP/1.1, gRPC).
• MediatR/handler pattern inside Application layer if deep layering is required.