Project architecture

Question

API

Colleagues!

Please help with advice where you can read about the architecture of a web project, in particular, the question of the interaction scheme between front-end and back-end is very interesting through requests to the API on the server (back). What are the pros and cons of this solution in comparison with the classical architecture of the project. As far as I know, twitter worked according to this scheme, but later left it.
I would be grateful for the links, as well as your opinion on this matter.

Answer 1

In the book “Development of Highly Loaded Systems. Based on the materials of the HighLoad++ 2010-2011 conference.

Answer 2

I won’t tell you the exact links, but I can suggest keywords: NoBackend movement, AngularJS, Firebase, Polymer, Shadow DOM, MeteorJS.
In addition to what I read in your comments to the answers, I can add that the backend will also have to be left with logic that the user should not have the right to influence. For the rest, you are correct.

Answer 3

I do not understand the essence of the issue.
In this case, the API differs from a set of actions only in that it is documented.
Further, what do you mean by architecture (I don’t understand from which side you look at the problem)?
If the question is whether to create a completely AJAX application, then my advice is simple - no. Because it greatly delays development and complicates the code. In server languages, such as PHP, people write something like that, but with JS, in general, everyone has trouble without exception. And not even because they don’t know how to write, but because the deadlines are tight and they do it so that it would be faster.