Scenario Title: how does system a use the page of system B

Most of our systems are independent , even A、B The system has interaction, which is also the interaction of the data layer , It is satisfied by calling the interface , But recently received such a demand .

A The system adds a new button , Click on the open B Systematic B.B page , from B The system goes directly B.B page , It's better than from A There are fewer buttons and fields in the system .

Train of thought

Write a separate page for this , Then all interactions are called by the way of the back-end interface .

advantage

The idea is simple and easy to understand , It's easy to develop .

shortcoming

Low code reuse rate , Poor maintenance , If a common field is changed, then two pages need to be modified .

Next time if C The system also needs B.B The page doesn't have to be redeveloped again ？ Or next time C System needs B.C page ？ Such development does not conform to the code specification .

Train of thought two

The conditions for the establishment of the above scheme are ,B The system must have a complete user role menu function , That is, you can control whether the menu is displayed or not through permission .

In fact, the last thing is ： Set up a special user who can only access specific pages and specific buttons .

advantage

Multiple reuse of one code , In the future, if xx System to access B System page , Add a user directly and configure it , The code is generic .

shortcoming

It's a little troublesome to think about it