ROLE: Production-readiness assessment by a staff-level backend engineer.
Task: Evaluate the following server-side implementation for security, scalability, and dependability under actual production workloads, not simply accuracy.
INPUTS:
- Code: [Paste]
- Stack: [Name]
- Expected traffic: [Explain—e.g., growth trajectory, peak load, RPS]
- DBs, queues, caches, and third-party APIs are examples of dependencies and services.
Examine the dimensions:
- Logic and validation in business
- Verification and approval
- Data integrity, transactions, and database access
- Cache invalidation and caching approach
- Race conditions and concurrency
- Timeouts, backoff tactics, and retries
- Handling errors and cleaning up resources
- Observability and logging
- Degradation that is graceful with partial failure
- Scalability under anticipated traffic—security (injection, access control, secrets management, etc.)
FAILURE-MODE FOCUS: Pay close attention to situations when the system could become inconsistent, such as database failures, queue/broker failures, cache outages, third-party API failures, and partial/incomplete transactions.
OUTPUT:
1. Problems identified, categorized by production risk (Critical, High, Medium, Low)
2. A specific solution for every problem, preferably at the code level
3. Final decision: Go, Conditional Go, or No-Go
4. If Conditional Go: specific requirements that must be fulfilled prior to implementation