Author: Li Chunqing assessment method is the key to master the middleware To select a middleware technology to meet the requirements necessary to understand their needs, have to make a technical assessment of middleware software. We don't talk about how to understand your needs, just talk about how to do technical assessments in middleware. With the wide application of middleware, end users and application developers are often facing this issue. There are more and more types of middleware, and the functional characteristics of a single product are increasingly rich. If they must not collapse, they will fall into endless details. Therefore, it is very important to master the method. Choosing the middle parts must not only pay attention to technology, we must consider the factors related to manufacturers, the services, prices, etc., but the technical satisfaction needs is undoubtedly the first place. As a "standard function" of similar middleware, you can use your specific needs to see if this software is applicable, or it is good. If you know the type of middleware software you have to evaluate usually - we call it "standard function" - you have a basis for reference. You can see if you have these "standard features" in front of you, if not, is there an important impact on you. What is the "standard function" of various middleware software? There is no standard and absolute answer for this issue, but you can have a number of answers to most manufacturers, you may wish to use it as a reference. If you can't find ready-made, you can try it yourself. Introduce the product of the product to each manufacturer, do a comparison. "Standard Features" is usually included in the common function of the product. Grasping the functional requirements, non-functional demand and technical standards. We can divide the demand and non-functional needs of the software when designing a software. Functional requirements indicate the functions that the software must perform, define the behavior of the system - that is, the software to give the determined output must be processed or converted under certain input conditions. Functional requirements are typically the "hard metrics" of the software feature - such as "reliable transmission of messages in distributed environments"; non-functional demand does not describe what software do, how to describe how software is described. Non-functional demand usually serves as a "soft indicator" in software design - such as "system has scalable". To this end, we can refer to the functionality corresponding to the functional requirements "functional feature", and the function corresponding to the non-functional demand is called "non-functional feature". Assess a middleware software, the most important thing is to view the functionality of this software, including functional feature and non-functional features, in line with our requirements, or in line with most people's usual requirements. If you know the "standard function" of a kind of middleware software, you can further divide it into "functional feature" and "non-functional feature". If you don't know, you only need to start from your needs, study if you have the "functional characteristics" and "non-functional characteristics" in front of the middleware to meet your functional needs and non-functional needs. The middleware is universal software in support position, and its technical standardization is of great significance. The support of the technological standards is manifested as several aspects of using standard APIs, using standardized technologies and standardization functions. Middleware support standards often mean that users and applications are smaller for manufacturers, and application developers learn to use a new product, and the middleware software can be interoperable with more system, technology is more open. Therefore, assessing a middleware must not only look at whether it has a certain function, but also to see if this feature uses a standard technology. Functional feature is the functional feature of the basic feature of the middleware is the basic feature of a middleware software. Different types of intermediate parts are first manifesting as basic functions, so we cannot summarize a set of general "functional features" suitable for all middleware doors. For a specific middleware software, we can extract its functional feature. We assume that a middle part is positioned to resolve message transmission, management, and control issues between senders and recipients in a step-by-step environment. The software provides a variety of messaging methods, supporting multiple messages, providing reliable transmission Waiting for service quality control mechanism, the software supports multi-system platforms, supporting high throughput business processing ....
