Backend APIs and data systems

What this bullet means

The employer wants backend features that can receive requests, store data, return clean responses, improve speed with caching, and pass events between systems.

Sample app idea

Claims Event Processing API with policy and claim records, a cache for lookup data, and queued status events for follow-up processing.

Main build outline

1. Create API endpoints for listing claims, viewing one claim, updating status, and adding an internal note.
2. Store core records in a relational database and include a simple lookup table for claim statuses.
3. Add a cache-friendly service for status labels or policy lookup data.
4. Represent status changes as simple queued messages or outbox records for later processing.
5. Document API routes, data tables, cache use, and message flow in a small technical README section.

Portfolio proof

• API route list with example request and response shapes.
• Database schema screenshot or entity diagram.
• README note explaining cache and message flow decisions.

Minimal documentation

• README with the business problem, screenshots, setup notes, and technology stack.
• One requirements note that maps the job bullet to the sample feature.
• One test plan note with happy path, validation, and edge case checks.
• One honest portfolio note that says this is self-directed practice, not employer work.

Modern .NET stack

• Blazor Server or ASP.NET Core Razor Pages.
• C# services with validation and dependency injection.
• SQL Server locally, then SmarterASP SQL Server or Azure SQL.
• Optional Azure App Service, GitHub Actions, Docker, and AI helper feature.