How amrut-pol-mp/grpcservice works
Project type and purpose
• This solution contains two collaborating .NET Core 8.0 services:
• GrpcService: a gRPC microservice exposing CRUD operations for Organization, User, and User-Organization Association.
• HttpService: an ASP.NET Core Web API acting as an HTTP façade that forwards incoming REST calls to GrpcService via generated gRPC clients.
• Purpose: decouple domain logic (in GrpcService) from HTTP/REST transport (in HttpService), host SQL Server in Docker, and auto-migrate schema on startup.
File structure
• Top-level:
• GrpcService/
– Protos/: .proto definitions for each service
– Controllers/: gRPC endpoints implementers
– Services/: business logic interfaces + implementations per aggregate
– Data/: EF Core DbContext, Entities, Repositories
– Common/: shared helpers (DI, pagination, result wrappers)
– Migrations/: auto-generated EF Core migration snapshots
– Program.cs + appsettings*.json + launch settings
• (HttpService would mirror a standard ASP.NET Web API layout with Controllers, Clients/Protos, Startup/Program)
• Architectural pattern: layered (Presentation→Service→Repository→Database), with gRPC transport, EF Core ORM, DI.
README for additional insights
• Confirms a dual-project setup (GrpcService + HttpService)
• Docker-hosted SQL Server with automatic EF Core migrations
• Tech stack: .NET Core 8.0, gRPC, ASP.NET Core Web API, Docker, SQL Server