Micro service is a very popular topic recently, sentient beings will talk about micro service, however, in practice, we found some projects, seemingly with micro service technology, but to make the application of the service, rather than achieve a goal, but increase the complexity of the architecture, the shame and therefore, before the service, it is necessary to make clear what is a service,
1. The bureaucracy is not as a service
Wu Yi county in hebei province takes six times back and forth to do a passport, a child is born to run social security bureau in shenzhen, neighborhood office, police station, these are a sign of low degree of service, the higher the degree of bureaucratic, as a service, the lower the degree of buying a house is relatively better, in partnership, water, electricity, gas "one-stop" work style,
2. The chimney is not as a service
The latest on business, using the system, e I system, s system several applications, such as after a long period of optimization, the experience of these systems are fairly good, but always feel very strange, to use problem in what place? Many times when you need to find a want of information, such as flight information, you often don't know what is going to check in the system, system, e I system, s application system is brand and word of mouth is very good, but under the scenario of service rethinking, we easily found that the application of the chimney is not as a service,
3. The hyperlink is not as a service
Since the chimney is not as a service, that I use hyperlinks to each chimney together, is it as a service? Obviously not, simple hyperlink to make things worse, not better, a hyperlink is like a one-way door, in order to get through two rooms, we need to install two one-way door, room for more time, the number of door more, finally formed a what? Yes, a maze,
Service System, not only the related function together, but the organic integration, simplified into One System, can let users based on the current scene feeling smooth processing end-to-end business, without having to jump between different style System everywhere so that scratching their heads,
4. The REST is not necessarily as a service
I made a application, foreground, the background, the front desk through REST (or SOAP, RPC, etc.), call the background is the service? Actually otherwise, this may also is a chimney, a disguise the chimney,
5. Single application of service does not necessarily not
As a service (SOA) is a method of building distributed applications in essence is to realize the ability of reuse in a distributed environment, monomer usually with micro service application, monomer with SOA application did not oppose, monomer applications can also expose enough service for other distributed applications to use (and the difference between the chimney), so as to realize the reuse of value-chain,
In addition, the monomer architecture does not necessarily is not a good architecture, it depends on the complexity of the application, a start-up company, to conduct business on the Internet -, due to the scale of business, business complexity is limited, not the code number of farmers, at this time, monomer architecture is the most appropriate, even for large companies such as huawei, in the field of some independent, if a single application can be a very good cover a complete business scenarios, monomer architecture is still appropriate,
6. The structure of the organization as a service to realize service,
As the saying goes, organization structure decide the technical architecture, a funnel type of organizational structure, it is easy to cause the chimney of the system, to achieve service, must break down in the organizational structure of a team with a chimney, into a service-oriented organization structure, the application of the front and back should adopt a completely different design method, the foreground of the UI is completely user-centered design, and the background of service design in business as the center, the front desk and background belongs to a different team, best to avoid intense physiological impulse, they build the chimney
In view of the complete scene of service is good,
Split scenarios lead to fragmentation of experience, good service is aimed at a complete scene design, let the user in the end-to-end scenario has a complete, consistent, simple, clear experience, what is a complete end-to-end scenario?
O travel is a complete end-to-end scenario, from the business trip application, to the ticket booking, hotel reservation, visa application, travel to the report, a * LONG * for the entire service,
O HTC is also a full end-to-end scenario, registered from application to application development, test, and resource application, configuration management, continuous integration, continuous delivery, operations automation, covering the entire link,
If separated, in view of a part of the scene design and other design another application scenario, it's easy to form the chimney, even if only for a complete scene any omissions, will lead to degradation of service experience,
Is the inevitable result of the large system as a service, business China,
Mentioned before, the front desk of the UI design is completely user-centered (order of my mission, I and my contract), and the background of service design is based on the business center (such as order processing, processing of the contract, the financial processing, etc.), users often want a one-stop experience, that how to "one-stop" work style to the user as the center of the front desk and dispersed to combine business as the center of the background? Answer is that the middle business, middle business to undertake the request of the front desk, and integrate the back-end services, in the process, can undertake specific mapping, integration, and regularization processing, automation, intelligent processing, this side confirmed IT China strategy, i.e. before the light, the strong, steady strategy, after
Overall, the goal of service, is through more as a service organization and complete service, the practice of building ROADS for full one-stop business scenario user experience (popular) to paraphrase, more decoupled architecture, so as to realize the whole process of online processing, higher business operation efficiency, increase business digital transition effect, we cannot overemphasize technology, and ignores the experience, therefore, to understand what is the service is more important than understanding what is micro service,
Next, again about my understanding of the micro service, attention please,
Click the link to join the sharing group: http://a.sccs56.cn/c/6613cd987dc465413b71f38f4ef4fc7d
Article source huawei cloud community: http://bbs.huaweicloud.com/blogs/2be9c4a9456d11e9bd5a7ca23e93a891