Online Game update Security first

Online Game update Security first

For the online online game server, change the code to put security in the first place, to avoid introducing errors.

When adding a feature or correcting an error, the scope of the change should be kept to a minimum.
Try not to create an impact on other existing functions.

For example, there are 2 design scenarios for implementing a feature.
One is to adjust the existing architecture so that the new features can be easily added.
The other is in the current architecture, special processing to implement new features.

The 1th scheme is the correct design, improved the original architecture, not only new features to add convenience,
It also enhances the flexibility of the system.

But for the online online games, the general choice of the 2nd option.
This approach is like sticking a plaster, where you need to put it.
In the same way, the code will be like a person with countless layers of plaster, bloated and difficult to move.
The only advantage is that this method is the safest.

After the schema is adjusted, it means that a large number of features have been changed, the impact is too great, and almost all functionality needs to be tested again.
There is no guarantee that the original functionality will be accidentally destroyed.

If you have unit tests, code changes can be bolder.
It's best to have automated regression testing. Regardless of any changes, all features will be automatically tested again.
But the automatic test of online games is very difficult. What kind of online game can enjoy the automatic regression test.

Sticking the plaster is reasonable. In order to avoid the line after sticking too much plaster, it is necessary to do more flexible design before the launch.
Best of all, just change the script after the line, without changing the code.

(Jin Qing's column)