This is the sixth day of my participation in the August Text Challenge.More challenges in August
preface
Recently, WHEN I want to reconstruct the management background project, I feel that the permission menu module is more complex when dealing with the new management background template, and the corresponding processing mode of each project will change with the demand and the change of the server.
Under this premise, I thought of whether I could remove the permission menu module of all projects and manage it in a unified way. Next, I sorted out some ideas
Access the background
Role management
Role management can be divided into role management of cost background and role management of individual projects. Each user in the permissions background is managed by the permissions background administrator, such as dividing projects
The project administrator added by the permission background administrator can handle any role of the current project, and only one project administrator can be assigned to each project
Menu management
When the role processing is complete, the menu corresponding to the project role is the same as the one we usually use. Of course, you can also have your own different way of processing, at this time you can consider building statistical menu management
Problems to be faced
concurrent
Because it is a background project, the call frequency is not too high and there is no need to worry too much about concurrency
disaster
The authority background may maintain the whole company’s management background project, if something goes wrong then it may be the collapse of the authority module of all the management background. How to resolve such emergencies is particularly important
Cost of iteration
From the perspective of the server, the permissions of each project do not need to be concerned, but there may be more permissions background and server authentication steps.
Front end aspect, can save development authority time, other basic is not affected
In terms of permissions, each time a new project is created, it needs to be iterated separately. How to solve the problem of grayscale publishing
Looking forward to
The middleware
The server side of the permission background is maintained by ourselves, so we can also introduce the concept of middleware to process data according to specific standards
conclusion
The above is my general idea about the permission background. After communicating with my colleagues, I found that I had to face some inevitable problems. In particular, disaster recovery and stability are not considered, and there is a big gap between the existing server stability plan
However, because I usually have less opportunity to contact the needs of this aspect, considering the problem will have some limitations, that is, do not know the seriousness of the matter without experiencing it, then I intend to experience 😁
According to my current ability to deal with it, it is definitely beyond my power to adopt the permission background method for the next large number of projects. I plan to improve this plan and build demo, and then consider the permission background with formal projects