The hottest middleware selection motto

  • Detail

Middleware selection Maxim

what kind of middleware your enterprise chooses becomes more and more important. It is very useful to carefully understand how to choose middleware, which will help you meet the needs of the enterprise with a suitable integration scheme. So, what kind of middleware do you choose? In other words, what kind of middleware strategy do you make for the enterprise

the development of technology and the evolution of the market have made middleware a key infrastructure for distributed applications. The connotation of middleware has become richer and richer, with more and more types, more and more complex technologies, and wider and wider applications. Accordingly, what kind of middleware your enterprise chooses becomes more and more important. It is very useful to carefully understand how to choose middleware, which will help you meet the needs of the enterprise with appropriate integration solutions. So, what kind of middleware do you choose? In other words, what kind of middleware strategy do you make for the enterprise

the complexity of middleware is not the fault of middleware. Building distributed applications requires solving complex problems. Middleware exchanges its complexity for the simplicity of enterprise applications. Hardware and software manufacturers provide you with too many technologies. You may have 5 operating systems, 6 databases, 7 network environments, 80 applications and 9000 network nodes, but you want to combine them into an organic whole to work together, which is too painful. Middleware is to solve this kind of problem. It tries to make your application development simple by shielding various complex technical details. Of course, middleware itself will be more complex, especially different types of middleware have been produced to meet different application needs. Middleware is very necessary for enterprise applications, but you need to choose

more and more middleware

from a macro point of view, middleware can be divided into three categories:

data class (d it is imperative to explore the new development path of plastic granulator technology ATA integration): it is used for data access, utilization and value-added, and this kind of middleware is used to build data-centric applications

process integration: it connects various applications or processes distributed on network nodes, Form a unified distributed application

distributed components: support component-based applications, the development direction of future applications, and the current competition is fierce

for the sake of clarity, we subdivide the middleware into the following 15 kinds:

although there are so many kinds of middleware, there are roughly five kinds of mainstream middleware: Data Access Middleware; Message oriented middleware; Transaction middleware; Object middleware; Application server. IDG's car carbon fiber composite, which has attracted much attention, has predicted the market situation of these middleware:

suggestions for selectors

vertically, you must make a choice when using middleware because of the many types of middleware. The selection should be made from the following aspects

select category: first determine the category and then determine the product

the particularity of middleware makes you have to determine your application type or specific requirements before selecting a specific middleware product, and then carefully determine which type of middleware to use. This is very important. For example, if your application type only transmits messages and has no special requirements for high reliability, high concurrency and high efficiency, you should choose message oriented middleware instead of transaction oriented middleware. If you are a typical mission critical online transaction processing system, you should choose transaction middleware. If you want to build distributed component applications, you should choose object-based middleware. If you want to build an application based on the web, you'd better choose a web application server. Here is a flow chart of selection:

of course, the actual situation is far from as simple as described in the figure. The functions of middleware are often cross cutting. For example, some transaction middleware includes the function of message transmission; Some object middleware inherits the characteristics of transaction middleware; Some application servers can take transaction management middleware or message middleware as a service, and so on. Therefore, in addition to the technical definition, the following factors should be considered:

technical maturity

the development history of different middleware is different. Because middleware involves a wide range of technologies, which are related to operating system, network, database and application, it takes 2-3 years for middleware to mature from its birth. The technology maturity of middleware is a problem that needs attention

integration with legacy applications

if you want to establish a connection between the application constructed by middleware and traditional legacy applications, you need to consider this problem

ease of use

the difficulty of using each type of middleware is also different. Some middleware is only a part of your application, and some middleware will give your application a new architecture. The current situation of applications, the level of application development teams, and the complexity of middleware itself will all affect the use effect of middleware


the cost of different types of middleware is different. For example, it is obviously too expensive to use message middleware only on the local area to realize data access. It is also insufficient to use transaction middleware in non transaction processing systems to transmit messages. In addition, the impact of technical training on development costs should also be considered

technical direction

some middleware is more traditional, while some middleware is the development direction. The choice of middleware is closely related to your grasp of the development trend of software technology. If the enterprise has decided to use component technology or web technology, you should choose the relevant middleware

choose services: affect success or failure

there are at least two reasons to emphasize technical support and services when choosing middleware. One is the complexity of middleware itself, which has been discussed above; Second, middleware is a new software branch. There are no relevant courses in universities, and few people in enterprises really know how to choose and use middleware. Therefore, using middleware requires more technical support than (1) selecting the research object: that is, it is certain that the object under force analysis uses other software. Support for middleware should include the following aspects:

manufacturers should help enterprises formulate middleware strategies

middleware is increasingly playing a decisive role in enterprise applications. Therefore, enterprises should formulate their own middleware strategies to make middleware play the greatest role for their own enterprises. Middleware manufacturers help enterprises formulate relevant strategies, so that enterprises can use middleware more fully and at ease. For example, different application types (traditional, component, web, etc.) adopt different middleware; The choice of different architectures in similar technologies (such as CORBA, EJB, DNA and other different systems in component technology), the choice of specific products in similar products, and so on

consultation and support of middleware based development

middleware based development usually requires "get started and send a journey" services, including setting up the environment (simulating the network environment required by distributed applications), middleware installation, development training, middleware based system design, development or grafting, middleware based application testing, etc. The support of middleware manufacturers will directly affect the quality of developed software

consultation and support in the process of using middleware

middleware is not only a development tool, but also a platform for application running. Therefore, it is very important to configure and tune the performance of middleware, which is like database, but middleware covers a wider range. There are experience values of different parameter configurations for different application operating environments and business volumes, and these experience values are most clear to middleware manufacturers. Therefore, the manufacturer's technical support for the use of middleware is very necessary

pay attention to the application environment: the software does have national conditions

it is worth noting that there are some differences between China's application environment and foreign countries, which are reflected in the following aspects:

the network communication status is uneven, and there are a large number of 9600bps communication lines. Foreign middleware products lack sufficient preparation for this

many large enterprises adopt multi-level tree structure in management, while foreign middleware products are mostly in shape structure

the application level varies greatly. Many industries have a large number of low version Novell applications and DOS applications. Most middleware is aimed at UNIX, windows and IBM systems

security, our government has clearly stipulated that we should establish a secure information system, and security products should be based on domestic. As a supporting software, middleware is closely related to system security. Therefore, the middleware should have replaceable security modules

choosing professional manufacturers: choosing the future

choosing manufacturers and choosing products are not the same concept. Because there are two kinds of diversity, one is that many manufacturers are making the same middleware product, and the other is that one manufacturer is making a variety of middleware products. Therefore, the selection of middleware manufacturers is an important part of the middleware selection strategy

due to the diversity of enterprise requirements for middleware, there are also different ways to choose manufacturers. There are two common phenomena. One is to pay more attention to the product itself and choose the best middleware products, regardless of the cooperation between different middleware and the strength of the manufacturer itself. Another view is just the opposite, choose a vendor with a variety of middleware products. Regardless of that view, it should be based on meeting your current and future needs for middleware. Because middleware is currently in a period of rapid development, with a wide variety, fierce competition, and requires more support services, it is always beneficial to choose a manufacturer specializing in middleware, otherwise it will bring problems to the future support and development. Just think, how can a manufacturer become your reliable long-term partner if it doesn't take the middleware you want to choose as its development direction

test: fitting is a good shoe

test is a direct and effective means to establish a simulation environment similar to your actual application environment, write simulation test programs, and test the functions and performance of middleware item by item. The test shall include function test, adaptability test, expansibility test, stress test, boundary test, damage test, continuous operation test, etc. Different kinds of middleware have different testing methods. But it must be able to simulate the real situation of using middleware

investigation: let the facts speak

if the test can't make you decide, you can also investigate the actual application cases and listen to the feelings of middleware users. Of course, the inspection should be very careful, including the application environment, application type, business volume, middleware working condition, configuration, middleware development and ease of use, manufacturer's support services, prices, etc. (end)

Copyright © 2011 JIN SHI