REST API with Minimal Endpoints in C#
The work-orders API with ASP.NET-style minimal endpoints and FluentValidation-like rule classes.
- Runs out of the box: yes
- Tests: no
- CI: no
- Docs: yes
- Used in production: no
Learning demo, not turnkey. This example is experimental: it shows an idea that works on the bench, but it has not been reviewed for production use. Expect rough edges and check with the owner before reusing it.
Purpose#
The C# implementation of the shared "work orders" API, built with minimal endpoint handlers and one validator class per request type. It passes the shared acceptance suite except for the cursor-pagination tie-break test, which is tracked as a known gap.
It is marked experimental because the team is still deciding between minimal endpoints and controllers for larger services.
Technologies & features#
- Technologies
- C#PostgreSQLDocker
- Features
- REST API Design
- Topics
- Application Architectureprimary
Lessons learned#
- Decision
Minimal endpoints keep each route short, but shared filters (auth, validation) needed a small helper to avoid repetition.
- Limitation
Cursor tie-break ordering fails one contract test when two work orders share a timestamp; a composite cursor is planned.
Try it#
git clone https://git.example.internal/business-systems/rest-work-orders-cs.git
cd rest-work-orders-cs
docker compose up --build # http://localhost:5000Commands come from the owner’s README. Credentials are never stored here.
