The rise of componentized software production is accompanied by two wars. One of the war is: the war of component production and code production method, the production method of this war component, and the advantage of its own efficiency is not war. Another war may be: the war of the basic assembly platform (middleware platform) and the application of the basic platform (business base platform), this war won unclear, suspense weight. Componentization software production is used to use assembled way, greatly improve the production efficiency of enterprise-level applications, and thus subvert the current software production method. It can be said that the software is software; after we will say: Software is assembly of components. Today we are in Zhongguancun, tomorrow we will find that many people are in software. Revolutionary changes are here. One day, we found that it is set, assembled, and it has become the "javelle" and mainstream of software production. This war, the victory is determined at the beginning; component-chemical software production is undoubtedly won. Membership software production brings a variation of the software industry, it produces its own ecological chain: 1. Tool providers for componentization, provide development tools; 2. Use development tools to open commercial components, provide components or component libraries; 3. Use the components developed by others and the component assembly software they develop; 4. Implementation and secondary development using software developed by others. The ecological chain manufacturers are interdependent to play the largest network value. Of course, some vendors may span several levels. For the proportion, my country's famous software company Shanghai Puyuan's EOS system includes development tools and development environment, management and maintenance tools, and support platforms, also provide commercial components and component libraries, and 2000 in Puyuan components. Multiple components are more considerable in this country, this is an important knowledge, experience and wealth. The focus of the second war is actually a problem: there is no need for an application base platform (business base platform). In other words, today's middleware cannot complete the role of the application base platform; if it is not, the development of the middleware can not expand and own these functions? If the answer is negative, it is also possible to add a layer in this ecosystem: 5. Application platform providers provide a platform for applications. Then, today's network resource level (network database, network operating system, middleware) provider, will encounter "ceiling" in the enterprise application market - application base platform. They will find allands, such as clacy, this level requires new software providers to occupy, or network resource-level providers develop newly different than middleware platforms. If the answer is yes. Then the platform will happen: the one of the war is: the existing middleware and application server providers facing up the functions. The other party of the war is the existing management software and application base platform provider penetrates their platform. They are different from each other, one from now on, is the angle of network and technology; another from top to bottom, is the angle of application and business. The advantages of each other are different, a good at network resource management; another good at business E The winner of the war belongs to the problem that can be seen from the opponent's perspective, can learn from the opponent, and turn the opposition of the opponent into its own advantage.
