Overview
What this challenge is about.
Read the data-access patterns across the 5 bounded contexts (Payroll, Timesheets, Benefits, Org, Reporting) and tag the 12 worst N+1 incidents from the last quarter's traces. Author a 4-page design document for Repository per aggregate root + a single Unit-of-Work per request, with eager-load specifications passed in. Refactor the Timesheets bounded context (around 14 controllers, 9 aggregates) end-to-end with characterization tests. Measure 5 critical Timesheets queries (timesheet-detail, payroll-export, manager-summary) for query count and p95 latency before/after using EF Core's logging + miniProfiler. Deliver design document, refactored context (PR series), migration guide for the other 4 contexts, and a 2-page performance report.
The Brief
What you'll do, and what you'll demonstrate.
Refactor one EF Core bounded context to Repository + Unit-of-Work and measurably cut query count and p95 latency on critical queries.
Earning criteria — what you'll demonstrate
- Apply Repository + Unit-of-Work patterns to a real EF Core codebase
- Design specifications that let repositories stay aggregate-scoped
- Measure query performance before/after with concrete numbers
- Hand off a refactor pattern to other bounded contexts
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Career mappings coming soon.