Direct conversion strategy

Direct conversion between the old system and the new system, the old system directly offline, the new system directly online.

Problems with this conversion strategy

After the new system goes online, users will find that there is a big gap between the original usage habits and the new system.

There are two solutions:

1. Design the guidance process and teach users step by step the differences between the new system and the original system.

You can use the IntroJS (AGPL, commercially charged) Bootstrap Tour (MIT free!) Introjs is a little bit easier to use just a few simple steps

The introduction of js
https:/ / cdnjs.cloudflare.com/ajax/libs/intro.js/4.1.0/intro.min.js
https:/ / cdnjs.cloudflare.com/ajax/libs/intro.js/4.1.0/introjs-rtl.min.css

Copy the code
Add attributes to the page element to which you want to add a bootstrap step
data-title="Welcome!" data-intro="Hello World!
Copy the code
Calling the js command
introJs().start();
Copy the code

It’s just a little expensive, 600 bucks for commercial license…

2. Provide the UI that completely simulates the old system (for example, the entrance of the old UI remains after the launch of the new version of blog Park)

User habits need to be re-cultivated and a lot of guidance and response from customer service is required.

The difference between the old data and the new data may be too great to require data migration and processing

Parallel transformation strategy

After the new system online, still use the old system, both exist for a period of time, provide users with an alternative, the benefit is that the user can still use their familiar systems, the downside is that the development and operations need to maintain two systems at the same time, is quite a challenge to the development and operations, at the same time because to take up the development of energy, There will also be an impact on the development of new requirements.

In my opinion, this kind of conversion is similar to AB test, in which some people are selected to use the new system and the experience of using the new system is collected. Others continue to use the old system.

In order to be compatible with the old system, the data on both sides generally need to be consistent, which often leads to heavy burden of technology. Finally, the new system and the old system may only upgrade some dependencies and introduce some new technologies, and the logic in the inner system is basically copied and pasted.

Segmented conversion strategy

The new system doesn’t replace the old system completely, it replaces it piece by piece,

For specific transformation, we can consider three strategies:

According to the function:

You can determine which of the main business functions in the new system are in urgent need of transformation, and replace the functions according to the degree of urgency. You can also replace the functions of the old system with those of the new system according to the degree of impact

According to the department:

Select a department to start the replacement, and wait until that department is successful before gradually expanding to other departments

By machine and equipment:

Interface makes no difference if the old system and new system, you can use nginx proxy way of running a server for replacement, to test whether the new system is able to bear the flow and pressure of production environment, this is usually used in the use of new technology, I remember my blog garden in use. Net core gradually replace, Every day to a high flow when the problem, crab is not delicious ah