Complete specification
Each brief defines the context, functional requirements, acceptance criteria and technical constraints.
Reduzer public projects
These are project specifications used to train Reduzer students. Each project defines the required system, acceptance criteria, delivery period, injected requirements and review process.
Each brief defines the context, functional requirements, acceptance criteria and technical constraints.
Additional requirements are released on specified project days and become part of the assessment.
Another developer must review the implementation, record findings and verify the resulting fixes.
Current briefs
2 projects available
Build the centralised system the team needed: one ingestion API that validates and enriches logs, routes them by service, writes them reliably, and surfaces live operational signals before customers notice the next outage.
Build reusable rate-limiting middleware that caps requests per caller, rejects excess traffic with the correct HTTP status and headers, supports two algorithms, and remains correct when several service instances process concurrent requests through shared Redis state.
How to participate
No application is required. Create a public repository, document your plan, implement the specification, publish the required evidence and ask another developer to review the result. Tag @reduzer_tech when you post the submission.