As a workaround, caching was implemented (server-side). In my opinion, it violates the principles of REST.
In fact, using a cache is a REST restriction that you MUST follow. Field dissertation 5.1.4 Cache: http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#sec_5_1_4 I suggest you read the entire dissertation (or at least a part of REST) before any additional questions.
they must suppress all kinds of affinity between clients and services (no session, etc.).
REST, . , . .
API REST .
, API REST. . facebook, google, twitter .. API . Ofc. API , REST SOA, RPC , , .
- API REST. (.NET) .
REST - ( ), , . SOA , . DDD - () .
API REST ( ). ( ).
. , REST API , REST - , , REST , ( ). , , ofc. / - .
API REST?
, . REST , SOA -. , , . , , , REST HTTP req-rep pat, (-) .
REST - , , . . public facebook api, fb api , - .
- HTML- REST , . . (URL-, ..) (, HATEOAS). , , , HTML- , , JSON-LD. .