Micro Services Series (three): Micro service decomposition and combination mode
How to better deal with multiple service data assembled question?
Wrote in the New Year:
the middle layer of data needed stitching, and sometimes we also call service aggregation layer, usually directly related to the front-end, APP and the like,
probably not return the data:
for example: space home, need to return different modules (such as data module 25), between the data independently of each other.
It could be:
for example: the person logging in to display the menu, you need to check the identity of this person, role, you can see the menu, but also to do with CRM check, remove the module data not purchased.
In this way, this layer is a lot of business, so-called mature framework is not the answer, at present can only be understood Coding of. We built a layer on top of the micro-service aggregation service layer, or the interface layer called the front desk? ?
In fact, many times, is the most likely to change this layer, and the base layer of micro-services + business layer is relatively stable, the general service aggregation layer great change. Previous cloud platform is not this layer, was greatly troubled, front-end staff have been complaining about the back-end personnel are not available interfaces to provide a one-time, requires repeated multiple calls to HTTP, is too slow; people can not stand the back-end part requires front-end staff, increase in their mature code logic, extended complexity, and continues to expand, more and more interfaces leading to a long, almost can not read the code. Thought to want to, and their own vision of the overall architecture-pit is a little step on the ah. Meanwhile, also understand the truth, not readily useful framework is the best solution, but to understand the essence, then repeatedly thought best practices, for our own use, is king.