What does SOA bring to us?

SOA is a service-oriented architecture, and no one agrees. However, each vendor has its own definition and explanation of what SOA is. Some people say it is an architecture, some say it is a methodology, but few people can give a convincing and easy-to-understand explanation. SOA will be appliedProgramDifferent functional units (called services) are linked by well-defined interfaces and contracts between these services. Interfaces are defined in a neutral way. They should be independent of the hardware platform, operating system, andProgramming Language. This allows services built in various such systems to interact in a unified and universal manner.

SOA poses a skill challenge to the entire IT organization, not just the architect team. In particular, SOA-like any other architecture, it brings a lot of difficulties to the application development team. After all, developers are creative elites who like freedom and do not appreciate too many structures. However, as an architecture, SOA imposes too many restrictions on developers.

The deployment of heavyweight SOA may involve a large number of teams involved and has a wide division of responsibilities. Medium SOA projects are generally completed by small and flexible development teams, during deployment, architects can directly deal with developers, testers, and other daily staff. In addition, if enterprises can use tools that support such a wide range of specialties, such a team-based tool can alleviate conflicts between many architects and developers.

In fact, these conflicts often come down to the governance issue-what policies should developers use when creating, releasing, discovering, and reusing services, and who is responsible for formulating and implementing these policies. Therefore, medium-sized SOA tools should also have support for such governance capabilities, so that application development teams and architects can participate in the formulation and implementation of policies together, rather than simply putting architects responsible for formulating these policies, this approach is impractical and usually caused resistance from developers.

In terms of interpreting the concept of SOA, various vendors are able to express their unique advantages. These vendors include not only old vendors such as IBM and Bea, but also new players in the Iona, panyuan, and tmaxsoft markets. While some traditional old middleware vendors are promoting SOA, some market participants have also begun to propose their own definitions of SOA, which leads to users' expectations for the bright future of SOA.

Having no choice is helpless, and having a choice is a kind of pain: when only one monopoly provider in the market has the right to speak, users have no choice. When there are many choices, users are often at a loss. At present, SOA has become the focus of the global IT market, and China has become the biggest potential market for SOA. For the SOA industry, the cultivation of the market requires open concepts. The advantage of a wide range of names or too advanced concepts is that it is a good thing to allow more manufacturers to gain a say in the market and give users more choices. The disadvantage is that, it is easy for users to have a few expectations on the business value created by SOA, but it is a bit confusing, and it is not conducive to the implementation of SOA.

No matter how advanced the manufacturer claims its SOA concept and how agile the implementation method, the purpose of implementing SOA is the same for the user CIOs, that is, to achieve business-centric implementation, improve the flexibility of IT system expansion and reuse of IT assets to achieve a flexible combination of business.

Although different vendors or individuals have different understandings of SOA, there is not much controversy about the goals that SOA can achieve, that is, to achieve the maximum reuse of enterprise IT assets, enables it to become more elastic, respond to the needs of business units more quickly, and implement real-time enterprise. From this perspective, what SOA is not important. What is important is whether it can meet the needs of users. Whether it's a black cat or a white cat, catching a mouse is a good cat. Whether it is the pioneer in the market or the market leader, whether it claims that SOA is a framework or methodology, one thing remains the same: Who has set up the most convincing SOA model user in China, who will attract more new users.

Two tips for correctly understanding SOA: Architecture and planning.

SOA is a good thing, but it is still a bit confusing. It is like a mountain. Looking at the lush area and looking at the sea of thorns, I really don't know which way to go. For the implementation team, SOA is not a product but an architecture; for the management team, SOA is not a project but a planning. If enterprises consider SOA from the perspective of architecture and planning, they will have a more practical understanding of its advantages.

The Enterprise Information Service System should transform traditional applications and governance models.

The most important part of China's enterprise informatization project is to transform the application mode and governance mode of the traditional system through an open application service system. This is not only a Chinese enterprise, but also a most effective implementation mode in the informatization process of all enterprises in our country.

Security risks have become a hard nut to crack in mobile information.

With the development of mobile informatization, many experts predict that more viruses and worms will spread to mobile devices such as smart phones in the future, which seriously threatens the security of mobile informatization. Currently, the top priority for users is how to effectively protect the various sensitive information stored on all mobile devices.

The most accurate explanation is that SOA will not only exist as a set of architecture, but a set of policies, practices, and even compliance frameworks throughout the implementation process.

I may not have pointed out what SOA brings. However, what I can clarify is that the appearance of SOA is the inevitable development of the original assembly language, the subsequent structured programming, and the popular object-oriented concept, it is also the most powerful impact on the past.