The first thing I did after I came to the new company last year was to choose a suitable development framework at the request of the leader. There is a familiar development framework before, Extjs+.NET is a simple three-layer, which is enough for the general enterprise background management system.
But now the front end frame of Extjs is basically eliminated, and the simple three-layer back end is also very outdated. But for the selection of frameworks, the newer the technology, the better. It is necessary to consider the team's personnel capabilities, the richness of online documents and related codes, and the ability to develop rapidly.
At the beginning, there were only two people in the team, one could only simply drag the server control and then simple C#, add, delete, modify and check the database. The other person just graduated for a year and has only done simple secondary development of the BPM system, and he doesn't even know how to use the array. Therefore, the focus of considering the choice of framework is the "survival rate", that is, there is a set of frameworks that include commonly used authority management and other complex and common functions. Layout technology, write and write simple additions, deletions, modifications, and queries in the background. This set of framework really exists. By chance, it is a framework written by the boss of a local programmer organization in Weihai. The technology used is actually based on bootstrap , aceadmin , jquery , HTML5 , C# , webservices , Redis , sqlserver and other technologies or tools. Through Integrate original design patterns. I tried it myself, and I feel that the technical requirements for personnel are very low, but it can make a better-looking system. System login, permission function management, data entry, report graphics display, export to Excel and other functions are all available. Except for writing some simple sql codes in the background, other basic configurations and pasting modified codes are enough. It is quite fast to get started. The boss told me that he was familiar with it. He developed a system with more than 50 function pages by himself in only two weeks.
Although the entire system is open source, it does not use any advanced technology. However, the leaders always felt that it was risky to base the enterprise system on such a framework constructed by individuals, and in the end they failed to make sense and passed the framework.
Then began the long road to find a new framework. But a clever woman can’t cook without rice. Any more advanced framework requires learning costs. But for non-professional software companies, does the company have too many projects to learn and practice? realized. Later, the two members transferred their parting projects and did not do development, and the company recruited me a person with relatively rich experience in .NET development, and another person with rich java experience was about to join the job. In this way, the direction of the selection frame has changed again.
First of all, we must consider the versatility of the architecture, because there are .net and java, so I tend to use the REST development method, and the front-end framework such as Vue.js can be used. It is unrealistic to use Vue.js to rewrite a set of commonly used interfaces, because everyone is not very familiar with Vue.js, and later discovered Alibaba's open source framework "Flying Ice". This framework contains many ready-made controls, and the front-end use is not a big problem, but the most important thing to choose a framework is to improve development efficiency, and it is necessary to include basic functions. This set of framework is just a front-end framework, and the methods used by the back-end to obtain data are not familiar to us, nor do they contain some commonly used functions.
By chance, I discovered the open source ABP framework, which contains commonly used functions and has a complete permission function (named ZERO), which feels a bit reliable. The specific functions are being explored and are to be continued. . . . . .