ITOO-Permission System (1), itoo-Permission System

ITOO-Permission System (1), itoo-Permission System

Since the end of the soft exam in March, ITOO has already passed two versions of its life cycle in March of this year. In March, some people have begun preparing for the soft exam in May this year, and we have another 3.0 development phase.

This identity is different from the previous two stages. From the examination system to the new student admission system, it is a member's identity. This time, five of us took over the permission system and I became the team lead.

Permission System, our main members are five boys, from the difficulties encountered in building the framework, to the integration of code, and then to the difficulties, to the whole.

With the framework, we have experienced what an architect is. from 1.0 to 2.0 factories, we have dropped from 3.0, replaced by IOC containers, and added Spring. However, when we build the framework, the dll version has caused such a problem, but I do not know, this is just the difficult start.

There are still many breakthroughs in 3.0, and unit testing is also a new blood. We do not need to add the console and then add various references to make better use of the Unit Testing encapsulated by, it really saves us a lot of time. unit testing can also test our own interfaces. For example, I am working on the role management module of the permission system and need to provide interfaces for the registration module, after I complete the interface, I can use the unit test to test whether my interface is correct. This is really a good tool for self-interest.

After setting up the framework, the permission system starts the code integration stage. In the early stage of 3.0, we wrote the Naming Convention document and the annotation document for everyone, striving to achieve the standardization. When code is exported, we find that the permissions are very high. Almost all of our interfaces are manually typed, And the UI specifications are not used. All permission systems integrate the code and modify the page; while guiding code, I gradually learned about the business logic of permissions and the relationship between roles, users, and resources. This confirms that the sentence is used to sneak into the night with the wind, so that everything is fine.

The permission system is a public service, with different foundations. The Business System of the evaluation system requires the permission system to serve all systems. Therefore, the permission system throws many problems, for example, the registered dynamic database creation and table creation, the secure exit of CAS single-point logon, and the implementation of dynamic database sharding, as well as the concept of AOP or AOP pool.

These difficulties are both a challenge and a kind of experience. They will be cracked a little later in the blog.