What are some good books on application architecture?

Question

Books

Please tell me if there is any literature describing the process of creating applications in general, and the difference between them.
The role of the backend, frontend, the difference between, say, a backend for a mobile application and a backend for a web service or website, what is the core of the application, API, REST, etc.
So far, only answers to specific questions have been Googled, and the whole picture does not add up.

Answer 1

There is nothing sensible about the architecture of applications. All I have ever seen is a description of one approach or another, an examination of its merits. There is no general review on this topic (I did not get it). To understand the issue of software architecture, start reading from here and follow the links from the see also block. This will probably be the fastest way. If something is not clear on this or that issue, read the articles on this topic (there are many of them even in Russian on all sorts of hubs and similar resources).
In this way, you can quickly master the terminology, which will allow you to further close the gaps in the whole picture as you read small private articles, understanding what is being said as a whole. Again, this (mastering architectural terminology) will allow you to correctly formulate requests for finding the additional information you need.
I did it myself once. Very well understood :)

Answer 2

there are a couple of books, I myself have been collecting for a long time, but there is really little information.
here is the link https://yadi.sk/d/TIjekwdAmiBWa

Answer 3

A.Larin advised me the following books:
- PRAGMATIC PROGRAMMER (simple, it's worth starting with)
- UML. BASICS
- ENTERPRISE APPLICATION ARCHITECTURE (difficult but interesting)
- REFACTORING: IMPROVING EXISTING CODE

Answer 4

there is a book , but there is one thing, but books get outdated very quickly, especially with regards to web development, so don't try to get too hung up on reading them.
Web application - works on a client-server architecture
The role of the backend and frontend is easy to understand, the backend server part (server) of the application, in fact, there is no difference between the backend of a service, website or mobile application, they perform the same function, collecting and processing data, providing data in a convenient format to the client. As for the client (in the particular case of the frontend), it can do a lot of things, the most common is the GUI (forms, tables, buttons, etc.), which allows the user to communicate with the program, enter data, receive data in various forms, produce pre- data validation (Always check the data on the server, be paranoid - don't trust anyone), and a bunch of other things.
API

API (application programming interface, API) is a set of ready-made classes, procedures, functions, structures and constants provided by an application (library, service) for use in external software products.
wikipedia

and so if the GUI is for a person, then the API interface for programs, for example, we need to get the exchange rate in the form of a table in our application, in this case we will just use the API of the service that provides such information.
REST is a good article

Answer 5

You can start with the book Perfect Code by S. McConnell. There are a lot of things on software design, but everything is generalized, without specifics.

Answer 6

Here for you to see

Answer 7

All with the upcoming!
This topic, apparently, is poorly formalized, and therefore somehow there are no particularly good books.
If you want to understand such issues, then the best way is experience. Participate in different projects, see how it works, figure out how it works, what are the pros and cons. Change jobs every two or three years to see different projects with different approaches.
Look at architecture from different angles. From the side of the manager (how much will development with such an architecture cost?), from the side of the user (Is it easy to insert everything, even the most crazy user wishes into such an architecture?), from the side of programmers (is it good to write for such an architecture?), etc. .d.
Beware of the subjective assessment of architecture - many consider any architecture invented by someone else to be bad. If a person scolds the architecture, get specific answers about why it's bad, not vague accusations like "not flexible", "archaic", etc.

Answer 8

related question: link