How fbadaro/rinha1-conc-net1 works
Project Type and Purpose
• This is a standalone backend microservice (Minimal API) implemented in C#/.NET 7.
• It is designed to run entirely in Docker containers, orchestrated by Docker Compose, exposing an HTTP API behind an NGINX reverse proxy.
• It uses TDD (xUnit) for integration tests, and includes background processing via hosted services (queue consumer, record sync).
File Structure
• Top-level “src” folder contains two projects:
• RinhaBackEnd – the production API service
• RinhaBackEnd.Test – the xUnit integration tests (runs against real containers)
• Docker artifacts: Dockerfile, .dockerignore, docker-compose.yml (plus override/testing), nginx.conf, run.sh
• App code organized into Domain, Dtos (Requests/Responses), Extensions, HostedServices, Middlewares, Program.cs
• Tests mirror controllers and domain logic under RinhaBackEnd.Test
• External resources defined in docker-compose: Postgres, Redis, NGINX
README for Additional Insights
• Technologies: .NET 7 Minimal API, Swagger, xUnit, Docker Compose, Redis cache, NGINX load balancer, Postgres
• Endpoints: health check, CRUD for “People” stored in Postgres, simple search and count
• Stress test via Postman collection
Key Points to Emphasize
• Both synchronous request/response paths and asynchronous hosted-service flows.
• How TDD/integration testing fits into the same architecture.
• Don’t overcomplicate: break the system into these core components and their interactions.