Twelve fatal mistakes in the most irrational exten

  • Detail

Twelve fatal mistakes in irrationally extending SOA architecture

common mistakes in adopting service-oriented architecture (SOA) are easy to understand and can be avoided with a little effort. Ignoring these mistakes (and thus repeating them) may cause all your efforts to introduce SOA to go off track and lose your advantages. Here are the twelve most common mistakes in the implementation of SOA summarized by Gartner

error 1: irrational SOA extension

there are too many services, and they are not ready to match the business model of the application. Such an SOA environment means that the application needs to be checked again after completion. Such an environment may have many services, a large number of documents, and rich new tools and middleware, but it lacks agility, incremental software versioning, or reusability

error 2: forget data

designing a service model is like designing a data model. Forgetting data in the processing process is easy to lead to poor service performance, which affects the integrity of the application. When designing services, strive to cooperate with the design model of the basic database

error 3: leave SOA to technicians

if most of the SOA process is left to the IT Department of the enterprise, the starting point of design services to optimize software performance and reliability will face risks and may not fully reflect business requirements

clarify that business interfaces are the essence of cross application integration or multi enterprise use

error 4: ignore the barriers of enterprise culture

one of the expected advantages brought by SOA is to enhance software reuse, but achieving this expected goal is a great challenge. Enterprise culture barriers will affect the effectiveness of SOA reuse. For example, if the IT department suffers from "not invented here", programmers, project leaders and architects will not trust the reuse services developed by other groups, or just hope to develop a complete set of solutions by themselves. The "not invented by me" syndrome will lead to redundant programming work, redundant personnel allocation and loss of opportunities due to lack of available resources, which reflects the main obstacles of SOA reuse mechanism

error 5: make sudden investment

many enterprises, especially those that think they have started late in SOA, tend to jump from previous doubts to sudden strategic investment. However, investing in large-scale SOA development without proper preparation and planning often leads to serious mistakes. Because it is a long-term stage to face the material business with better performance price ratio, enterprises should invest more in understanding the SOA project and cultivating the enterprise culture before carrying out the key SOA project. For most companies, gradual progress is the desirable way

error 6: wrong starting point

the most common wrong starting point is to follow the business needs of the first user who orders the service. For example, if the service is a user oriented application, you may design tools that meet their data needs. However, such a design process may eventually generate as many services as the user interface, which often leads to the problem of redundant and continuous growth of services. A more unified, systematic and effective method is to design a series of coupled information services around the business process or data model of the application

error 7: mistakenly thinking that everyone's ideas are consistent with yours

soa originates from a technical design pattern for advanced distributed systems. SOA is now a hot topic far beyond the programming community. When adapting to business communication, we should consider and recognize these differences at all levels

for programmers, SOA is a form of distributed computing, and its function blocks may be applied to other applications

for software architects, on the other hand, SOA plays the role of translation and eliminates the obstacles between different application products

for CIOs, service orientation is a future investment. Code reuse means reducing the cost and time of developing new applications

however, for CEOs, SOA can help it better respond to business needs and adapt to competitive business changes

error 8: choose dictatorship to fight against anarchism

independent IT projects, groups, departments and fields usually have a desire for autonomy, which can be regarded as "anarchism", because this will lead to the inability to implement shared goals in a large enterprise. The other extreme of such anarchism is dictatorship, in which departments and projects are forced to comply with central orders. Neither of these approaches can provide the necessary balance for a successful SOA environment. A well structured SOA environment usually includes a SOA center of excellence (COE), including all early participants and collaboration between independent projects or between different departments within the enterprise. The center of excellence should also minimize unnecessary interference to participants in the internal process. It staff can still retain their autonomy while working hard for the common goals of the company

error 9: underestimate technical problems

SOA users must understand the complexity of middleware. Although service orientation is becoming more and more popular and there are more and more SOA Based Middleware, there is still a great risk for novices to make wrong decisions. For a small-scale, experimental SOA project, point-to-point network service connection is adopted. If more than twenty or thirty services are configured, a middleware based intermediary, the SOA backplane, is used

error 10: allow a surge in the number of unshareable services

shared services promote the faster development of consumer application products, reduce development costs and make maintenance easier. If the average number of services per user application product is significantly more than 20% or less than 10% of shared services, this may mean that the number of shared services is not the best

error 11: over centralization

rather than imposing a separate, enterprise level SOA backplane, it may be more feasible and wise to adopt a federated approach. In order to prevent dust from entering the lens barrel or lens surface, the SOA plan of the company is divided into SOA domain, subsidiaries, business units or departments with the increase of tension. Each domain is jointly managed by a business manager and a technical manager. Each domain has its own specific SOA backplane and service registry. It is supported by a regional SOA center of excellence and is managed on the basis of government regulations

error 12: promote SOA before you are ready

an enterprise level SOA needs the support of senior managers and perhaps the board of directors. However, it is dangerous to seek the support of managers for enterprise level SOA too early. By the end of 2010, less than 25% of large companies will have the technology and organizational skills needed to implement SOA on an enterprise scale. (end)

Copyright © 2011 JIN SHI