Is it right to try to implement the logic in the background rather than in the foreground?

try not to be serious,

is the kind that the complexity of the foreground and background implementation is about the same, or the foreground implementation may be a little easier, are put in the background to implement

I think it"s better to do this kind of thing in the background, because the code specification of the foreground is not good, and most of the code is messy, and it will initiate two requests in the foreground, which is not good for performance. Merging it into one request in the background is more concise and elegant. I think

Axios vue.js spring-mvc java javascript

Mar.06,2021

There is no standard answer for

. You said you asked twice. He said that he designed it not only to support you as a web, but also to support app or provide services to third parties, and then no one wanted to change it, so there was a middle tier.
but as far as this example is concerned, I think the backend should implement a query interface similar to / person/?:gender , or two interfaces to query gender and all. If there is no logical difference between men and women, it is probably an interface.

is not why this logic
should not be a male and female ID 01 / owner 2
and then an API at the backend runs SQL to check the data in table 2 and then returns it to the front end
in fact, in your case, both the front and back ends do not involve some security information. In terms of performance, it doesn't have much impact on the difference between two requests and one request
and integration on the backend doesn't necessarily say how fast the performance is

is correct. But sometimes, when the backstage is unwilling to do it, and there is no one at the front end to talk to you, you have no choice but to compromise. no, no, no.

actually there should be a backend to do it. After all, one less interface is sent.
actually, the backend should not want to do it. It is also normal. The front end is also easy to use peomise all is also very perfect

the front end writes less logic, on the one hand, it is difficult to maintain later, and on the other hand, if the requirements change one day, it is too troublesome to change the front end code.

try to write logic in the background, but you have to write it at the front end. If you are not as qualified as he is, then write it yourself

has the landlord not understood the SinglePage single-page application? After the team specification is done, either the back end or the front end is fine. Relatively speaking, the heavy front-end mode helps to reduce the overhead of the server and can effectively reduce the cost.

I've come across this before. The backend
who is preoccupied with adding, deleting, changing and searching, and is not willing to do any logic at all, I think we still have to look at the implementation logic. Like this interface.
shouldn't men and women all be in the same table? no, no, no. If they only have gender differences, then
and then
pass a parameter-1 man
0 all
1 woman
wouldn't it be better to get the data like this?

Previous: Vue using custom instructions to bind to multiple dom elements will collectively trigger componentUpdated hooks

Next: How echarts modifies specific column colors through click events of other dom