Something from Microsoft Enterprise Library -- No.1

The Microsoft Enterprise Library provides a detailed help for the application. Program The Design and Implementation of maxcompute are introduced in detail. Get a lot of useful information:
1. Architecture
2. Common
3. Security
4. log & Instrument
5. expection
6. Data Access
7. Cryptography
8. Cache
9. Configuration

First, let's summarize my feelings from architecture.
A good application must have a good architecture or framework. How can this be a good architecture? I think it must be able to handle the following:

1. Stable and robust. Some people say that the Linux kernel is more stable than the Windows Kernel, based on the execution status after N consecutive hours. Many people say that Linux is safer and more stable. I think it mainly refers to its excellent kernel. Good applications must be stable and robust.

2. Security. The stability of a set of software is often linked to the security. Only when the security is good can the stability be improved. The security of Windows is already good. However, many vulnerabilities have been discovered by hackers. Therefore, for excellent software, security can only be achieved with the best efforts, but basic security assurance is necessary.

3. execution efficiency. High execution efficiency is a prerequisite for excellent software. Some friends said that it would take seven or eight minutes to start the ERP software they developed. I think their software is definitely not good. Sure enough, the friend's software did not successfully implement the application.

4. scalability and maintainability. The current software usually comes with a beta test, and a new version is upgraded until the stable version still needs to be patched. Why? Because the world is moving forward, no one can accurately predict what will happen in a certain period of time in the future. This requires upgrading and scalability of our software (if it is intended to be available for at least three years ). Good scalability must be characterized by simple extension development and convenient deployment and maintenance.

5. Portability. Portability often includes the flexibility and convenience of deployment.

6. Friendly. That is to say, the user experience is satisfactory. Good software should be easy to operate, well-arranged, and the interface can be viewed well. The help instructions are complete. In short, users can better implement applications only when they feel comfortable. (Like Windows, the dumbfounded it, the more beautiful the interface is, the more unstoppable it is .)

So how can we achieve this ambitious goal? According to previous summaries, many design ideas have been developed to meet functional requirements. In Microsoft Enterprise Library, some ideas are used to implement a feasible solution. The overall architecture scheme can be expressed as follows:

In this architecture, a common block (common Layer) is very important:
The common block contains the useful elements shared by multiple other application blocks. The dependency between other application blocks is reduced. Elements placed in the common block should follow the following principles:
1. The element does not depend on other application blocks.
2. elements do not depend on any persistent state.
3. elements do not rely on any third-party technology.
4. elements are not applicable to a special application model and are universal.