Yaya HTTP methods ke danganta da CRUD, kuma menene safe da idempotent ke nufi?

Misalai

PUT /users/42 yana aika cikakken representation kuma yana maye gurbinsa; PATCH /users/42 yana aika fields kawai da za a canza (misali { "email": "[email protected]" }).

Safe vs idempotent

Waɗannan halaye biyu ne dabam:

• Safe — method ɗin ba ya canza yanayin server (karatu kaɗai). GET, HEAD, OPTIONS suna safe.
• Idempotent — yin request iri ɗaya sau N yana da tasiri iri ɗaya da yin sa sau ɗaya. GET, PUT, DELETE, HEAD suna idempotent.

Me ya sa yake da muhimmanci

Masu hira suna tambaya wannan don ganin ko ka fahimci ma'anonin HTTP sosai don gina APIs abin dogaro. Bambancin safe/idempotent ba na ilimi ba ne kawai: yana sarrafa kai tsaye abin da clients, proxies, da CDNs ke da izinin yi. Methods na safe za a iya cache da prefetch cikin 'yanci; methods na idempotent za a iya sake gwadawa ta atomatik bayan network timeout ba tare da haɗarin kwafin side effects ba — shi ya sa client zai iya sake gwada PUT ko DELETE cikin aminci amma dole ya yi hankali wajen sake gwada POST (yana iya ƙirƙirar orders biyu). Kuskuren gargajiya shi ne amfani da GET don jawo side effects (misali GET /users/42/delete), wanda ke lalata caching kuma yana barin crawlers su canza bayanai ba da gangan ba. Zaɓen madaidaicin method — da girmama yarjejeniyar safety da idempotency ɗinsa — shi ne abin da ke sa API mai tsinkaya kuma amintacce don gina tooling a kewaye.