'business services' need multiple user information, a number of business found out of data, each corresponding to the user information, this time is to' customer service 'requests one by one,,,, or directly to take in the redis.
If one by one to the 'customers' request, is that calculate the abutment resources,
Take if redis, redis not, is still want to request 'customer service' search, this is not very troublesome.
Request to give ideas. Thank you.

CodePudding user response:

Redis is online (cloud server memory alone) database, general store after login system, online for user information,

Get data from redis, faster than to DB database with database,

And Java authentication online user information in redis, was not an intermediary service,

CodePudding user response:

Ah. Struggle.
I just think impassability, customer service is responsible for the management of user information, in theory to the user's information, will find the user service, rather than directly to redis or database can get (assuming the business layer development),
But when the business layer query a mass of data, business database refer only to the user id, no other information, this will be a go out to a service to users, must request many times feeling is not very good...

CodePudding user response:

If the business divisions, of course, the code from service