Thoughts on open-source projects in practical application

Before the opening, I would like to raise three questions. I hope to discuss with you 1. Why is architecture applied and what benefits does it bring to us? 2. Do the brothers in the garden directly use open-source projects in applications or apply them to projects after reasonable tailoring? 3. Can you tell me which open-source projects can meet industrial standards? I hope I can give some specific indicators (such as concurrency capabilities) to talk about my application first, which is based on. net 2.0 developed the old project, which uses the open-source castle, I have also seen countless people in the garden to pursue it, so I did not verify the selection of technology. Looking at its ideas and implementation, I think it is good. But when we test the efficiency, we find many problems, the most serious issue of concurrency. I hope you will discuss this issue here, to give me some feedback. First, describe the scenario: 1. My application deployment is deployed on multiple HP 380 machines, and the frontend is F5 Server Load balancer 2. The testing machine is configured with the same HP 380.3 and gigabit LAN. 4. The presentation layer uses monorail.5 in castle. The number of concurrent requests per second is no less than 500, and the number of daily visits is 1 million. Test Results: When the concurrency is small, the system passes smoothly. When the concurrency is 500, the system reports an empty reference error in the Velocity of monorail.

 

Conclusion

 

We should consider the following aspects when building the system architecture: 1. Understand the background of the project, including: user Group, number of users, business conditions, invested capital, human and material resources, and project life cycle. 2. Based on 1, plan the project and select the technology. What are the potential risks of the company's existing technical strength or platform supporting the project. 3. When selecting some open-source projects, you should not be on the cloud or verify them. 4. If the technology is strong, it is best for enterprises to build their own architecture system based on the idea of open-source architecture to facilitate expansion and tracking and modification of errors. 5. If you do not have 4 capabilities, we recommend that you use the original Microsoft technology for large-scale projects (high concurrency and high reliability, through this practice, we found that Microsoft's original ecological technology is still able to withstand the test. 6. In some small-scale projects, the use of some open-source projects has advantages and disadvantages. Finally, the architecture is not static. The technical solution should be tailored based on the project requirements and application context. In my opinion. the maturity of net open-source projects is not enough than that of java (not to mention. net is not as good as java), especially the lack of large project application cases, and industrial standards, Hope. net open-source projects are a lot of fuel. At the same time, I hope you will talk about your experiences in the application of open-source projects, such as Castle, nhib.pdf, Spring. NET, Quartz, and log4net. Supplement: you are welcome to make a brick, but I hope it will be a practical discussion. For example, you think that the open-source project has high reliability and high concurrency, and has been tested on a large scale, I think this discussion is more objective.