Back-end

Outcome: Complete the task with Back-end (Backend). User context: Alla cassa, il backend controlla le scorte, addebita il pagamento e salva il risultato dell'ordine. Technical concept or control: Back-end (Backend). Why it fits: Metti regole affidabili, dati condivisi, integrazioni e lavori che richiedono un server sul backend. Do not use it when: Non fidarti mai solo dei controlli lato client per la sicurezza o il denaro. Engineering requirements: Define inputs, outputs, contracts, and rules that must always hold. Set authorization and input checks. Define failures, timeouts, retries, one-time effects, data moves, and compatibility limits. Operations: Add useful signals and logs that hide sensitive data. Set capacity limits and write an operator guide. Test recovery and rollback. Acceptance criteria: Contract and failure-path tests pass. Data and authorization rules still hold during retries and partial failures. Check performance limits, monitoring, recovery, and rollback. Evidence and limits (evidence boundary): Nessun singolo standard ufficiale controlla l'intero termine. Il suo significato può cambiare tra team, piattaforme o framework. Unknowns to confirm: Where the code runs, data stores, traffic shape, consistency needs, and the security boundary. Also confirm the compatibility period, service goals, and rollback limits.