// the find
asc-lab/dotnetcore-microservices-poc
Very simplified insurance sales system made in a microservices architecture using .NET Core
A reference implementation of a microservices-based insurance sales system in .NET, built to demonstrate CQRS, event-driven communication, and service discovery patterns across ten separate services. It's aimed at .NET developers who want to see these patterns wired together in a realistic-ish business domain rather than a toy 'ToDo' app.
It actually shows heterogeneous data access per service instead of picking one ORM and pretending that's realistic — NHibernate in PolicyService, Marten (Postgres as event store/doc db) in PaymentService, Dapper elsewhere, so you see the tradeoffs side by side. Both sync (REST via RestEase) and async (RabbitMQ) inter-service communication are demonstrated in the same request flow (PolicyService calling PricingService), which is the part most tutorials skip. Accompanying blog series walks through the reasoning behind each architectural decision, not just the code.
Eureka + Ocelot + RawRabbit is a 2018-era stack frozen in time — RawRabbit is unmaintained (last release years ago) and Eureka for service discovery is an unusual choice outside a Java shop; anyone adopting this as a template today would be pulling in dead or awkward dependencies. No Kubernetes manifests or Helm charts despite this being a textbook 'why you'd want orchestration' architecture — you're stuck with docker-compose for an 8+ service system. No distributed tracing (no OpenTelemetry/Jaeger) despite the whole point being to observe cross-service calls, which makes debugging the async RabbitMQ flows in practice harder than the README suggests. The manual setup instructions (separate Postgres, RabbitMQ, ElasticSearch, Eureka via Gradle) signal this hasn't been touched to modernize onboarding in a while.