Backend

Outcome: Complete the task with Backend (Backend). User context: Lors du paiement, le backend vérifie le stock, débite le paiement et enregistre le résultat de la commande. Technical concept or control: Backend (Backend). Why it fits: Mettez les règles fiables, les données partagées, les intégrations et le travail nécessitant un serveur dans l'arrière-plan. Do not use it when: Ne vous fiez jamais uniquement aux vérifications côté client pour la sécurité ou l'argent. 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): Aucun standard officiel unique ne régit l’ensemble du terme. Sa signification peut varier selon les équipes, plateformes ou frameworks. 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.