1. The service layer made RPC extracted independent deployment internally provided interfaces, all web applications via RPC adjustable service;
2. The more users, such as management side, the side B, C, provide multiple web service (the three major characteristics of Java know, will abstract).

CodePudding user response:

From the point of the problem of the LZ, I think LZ might be a flexible, will only do (or just want to do what they will, unwilling to learn new things, and then complain about something new is not good, this kind of mentality to adjust,

Micro service is a trend, the large system into small, small system into small system using RPC calls in each cluster, it's a common architecture
So
1. The service layer made RPC extracted independent deployment internally provided interfaces, all web applications via RPC adjustable service;
Foreign can be a web application, but the internal efficiency of RPC is likely to be higher than the web application (a web connection to create can be very time consuming, the RPC remote call efficiency is akin to a local call), so the cluster internal micro service in order to more efficient with RPC with some appropriate call each other? And then provide an API gateway is a web application,

2. The more users, such as management side, the side B, C, provide multiple web service (the three major characteristics of Java know, will abstract).
If all the client with the same service, the service is out of question, whether all the client can't handle business? Is divided into multiple services, in order to avoid a service is bad, will not affect the other client to use other services, said again, more services are not necessarily more processors, the same program packaged into a jar package by multiple tomcat to use at the same time, each tomcat is a web service, and independent from each other (a bad does not affect the other normal work), three features of abstract this is a Java can solve the problem?

So before talking about the bad not bad, ask yourself if you really understand the meaning of the architecture,

CodePudding user response:

Look at the business requirements and project scale, mixed and disorderly,

Object-oriented also is not everything. There's mastercard & otherwise you also didn't what python,

CodePudding user response:

reference 1st floor qybao response:

from the point of the problem of the LZ, I think LZ might be a flexible, will only do (or just want to do what they will, unwilling to learn new things, and then complain about something new is not good, this kind of mentality to adjust,

Micro service is a trend, the large system into small, small system in the small system using RPC calls in each cluster, it's a common architecture

Don't stir, you put the micro pure RPC services make it, so you still have this architecture is especially common rotten, do bad thought oneself is right,,,
Do you know what is micro service?? What you said is a small system, but you didn't use, rotten thought he was right

CodePudding user response:

Can you use? Then you to tell me about your good architecture, said come out to let everyone amazing?
Is this mindset, you are good, is not bad, is unwilling to accept new things, new challenges,
If everyone like you a layer of constant, so IT is no new development,
Back to you just want to persuade you to adjust your attitude, not to quarrel with you, your architecture bad not bad didn't anything to do with me, do you think you cow you overthrow your boss, your clients without bites is to see others disagree here,

CodePudding user response:

reference 4 floor qybao response:

can you use? Then you to tell me about your good architecture, said come out to let everyone amazing?
Is this mindset, you are good, is not bad, is unwilling to accept new things, new challenges,

You see what I don't want to accept new things??
Multiple small micro service system is by doing the gateway polymerization of an application, if you are doing RPC again pack a layer of web aggregation, I would say it is good or bad,
Online open source springcloud example, basic for a class of service, users only, if you want to service oriented class more users, how to do?? Bad architecture of 2 has to solve