First, give conclusions that can be used for decision-making
Diffy's secondary development should be tiered. Brand entrances, business portals and complex interactions are prioritized at the front end of independence; enterprise systems capacity is linked through API, plugins or peripheral services; only core needs that cannot be met by standard extension points enter the source-code branch. Each core change is documented in terms of objectives, documents, data structure, upstream equivalents, testing and removal conditions.
What conditions need to be identified before judgement is made?
The same question may have different answers under different business, data and project phases. It is suggested that the following conditions be checked and that the common findings on the web be incorporated into their own projects.
Suggested order of advance
First, we'll be clear about the target and the border.
Creates a list of current versions, dependencies and all custom points.
Validation Key Dependence
Moves the externalable function to plugin, API or stand-alone service.
Development of assessable outcomes
Complete the automated test and migration statements for the core changes retained.
Make sure you decide the next step with the real results.
Each upgrade is preceded by exercises, regressions, backups and distribution of greyscales.
How do you understand it in the actual business?
The enterprise has modified a large number of front-end Diff pages for the client portal, and has also directly added client suites to the core table. Subsequent upgrades involve interface conflicts and database migration risks. It is more feasible to maintain the customer portal, package and metering in a stand-alone business service, with Diffy being called through a stable interface, with minimal core changes to the platform capacity that is actually needed.
The easiest pit to step on.
The change points are organized only after the project is over, and they can no longer be traced.
Upgrade script directly upstream of the operation of the production environment
Check pages only, without returning to knowledge, privileges, tools and data
How should we end up receiving and confirming?
The upgrade requires a re-testing of tasks, role privileges, knowledge references, workflow, interfaces, logs and backslides.
When preparing to communicate with suppliers or internal teams, it is recommended that current processes, representative samples, existing systems, planning time and budget levels be brought. First, the unknown items are clearly marked, and then the decision is made to use diagnostics, PoC, fixed-range projects or ongoing research and development, which is usually more reliable than a direct demand for a price and duration without borders.