REST (Representational State Transfer) salon gine-gine (architectural style) ne na aikace-aikacen network, wanda Roy Fielding ya ayyana. Ba protocol ko ma'auni ba ne — saiti ne na ƙuntatawa (constraints) waɗanda, idan aka bi su, suna sa API mai iya faɗaɗawa, mai iya cache, kuma mai sauƙin tasowa. API "RESTful" yana tsara komai a matsayin resources (users, orders, products) waɗanda URIs ke gane su, kuma yana sarrafa su ta amfani da HTTP methods na ma'auni.
GET /users/42 HTTP/1.1
Host: api.example.com
Accept: application/json
HTTP/1.1 200 OK
Content-Type: application/json
{ "id": 42, "name": "Ann", "email": "[email protected]" }
URI /users/42 yana ba resource suna; GET shi ne aikin; JSON shi ne representation. Wannan haɗin — sunaye (nouns) a path, kalmomin aiki (verbs) a matsayin HTTP methods — shi ne zuciyar REST.
REST shi ne salon da ya fi rinjaye ga web APIs, don haka masu hira suna amfani da wannan tambaya don duba ko ka fahimci dalilin da ya sa yake aiki, ba wai kawai za ka iya rubuta shi ba. Ƙuntatawa biyu da suka fi muhimmanci a aikace su ne statelessness (kowane request yana ƙunshe da kansa, don haka za ka iya sanya kowane adadin servers a bayan load balancer da scale horizontally ba tare da sticky sessions ba) da uniform interface (URLs masu tsinkaya, masu mai da hankali kan resource tare da HTTP methods da status codes na ma'auni, wanda ke nufin clients ba sa bukatar logic na musamman ga kowane endpoint). Amsa mai ƙarfi tana haɗa ƙuntatawa da fa'idodi na zahiri — statelessness yana ba da damar scaling, cacheability yana rage load, layered system yana ba ka damar shigar da CDNs da gateways — kuma tana lura da cewa yawancin APIs na "REST" masu amfani ne maimakon cikakkun RESTful (kaɗan ne ke aiwatar da HATEOAS). Fahimtar waɗannan ƙuntatawa shi ne tushen kowace shawarar ƙira ta REST, daga zaɓen status codes zuwa versioning.
Ɗakin karatu na tambayoyin hira na IT tare da amsoshi cikakke — daga Junior zuwa Senior.
Ba da Gudummawa