What really makes schools and integratedrs nervous is not the new campus itself, but rather...Once the new campus is connected, will there be any problems with the old campus?。
The old school complex has been running for years:
-
User size stabilized
-
The billing rules are mature.
-
The complaints rate is low.
Any system-level fluctuations are infinitely magnified.
Therefore, a qualified campus network Authentication & Billing system must answer one question at the outset of its design:
How to move the old campus without affecting existing users“Put it through.”。
I. THE OLD SCHOOL REALLY“It's not gonna get affected.”What is it?
In the real project, what's called“It doesn't affect the old school.”Not a slogan, but a clear technical boundary:
-
The existing certification process cannot be changed
-
Login is no change
-
NATHHELL_SEAMLESS_AUTH
-
-
The billing rules cannot be rewritten.
-
The existing package, cycle, strategy remain intact
-
No re-costing for older users
-
-
Network path cannot be adjusted
-
The old school district exports and operators' access patterns remain unchanged
-
If a campus network Authentication & Billing system needs to be connected to the new campus“And adjust the old campus configuration.”That in itself is a symptom of the existence of structural problems.
II. WRONG PRACTICES: READING A COURSE AS“Old school complex copy.”
Many systems are expanding the new campus using the most cost-effective but risk-most approach:
-
Copying old school strategy.
-
Reuse the same logic
-
In the same system.“Stug”New campus.
This approach is short-term, but it is almost inevitable that the long-term problem will be:
-
New campus strategy re-engineered.
-
The new campus is volatile and affects overall performance
-
New campus check. Logs mixed together.
There is only one reason:
The system's not working.“School complex”Designed as a truly stand-alone operating unit.
III. THE RIGHT PREMISES: THE SCHOOL MUST BE“Logical separation”Field of the running area
The mature campus network Authentication & Billing system must have a capacity at the structural level:
Each campus is a logical, strategic and risk-controlled field of operation.
This does not mean:
-
Multiple systems
-
Multiple databases
-
Multiple carriers
It means:
-
Same system, multi-run domain coexists
-
Uninterrupted, but undisturbed.
This is the new campus.“No risk access”Preconditions.
IV. Dismantling of the real system process for access to new campuses
In the stable campus network Authentication & Billing system, access to new campuses is usually based on the following steps:
1 ⁇ New campus as“New Run Field”Registration
The system will not directly insert new campuses into the existing campus configuration, but rather:
-
Create an independent campus logo
-
Independent authentication strategy packaging
-
A stand-alone billing strategy
From the first day of the system, the new campus is not.“Old school annex.”。
2- Certification is independently configured and does not inherit the old school district logic
Even if the authentication is in the same way (symbol / / work number / cell phone number):
-
The new campus is still independently configured.
-
Seamless Authentication
-
Do not share session control logic
The point of this step is:
Any abnormal certification of the new campus will not pollute the old school status machine.
3 Rules governing the accounting of fees“Copy structure, no examples”
The mature system distinguishes between:
-
Rule Template
-
Examples of actual entry into force
The new campus can quote a fee template that matches the old school complex, but it generatesExamples of independent fees：
-
Bill Independence
-
Cycle independence
-
Wind control independent
Even if the new school district billing is not properly tested, it will not affect the old campus's valid bills.
4% New campus traffic first“Observation”After“Discharge”
In real projects, the new campus is usually not fully released once and for all:
-
First, let the test user be managed.
-
Put some more dormitories or areas on.
-
Last whole switch
The campus network Authentication & Billing system will be used to create a new campus:
-
Independent statistics
-
Independent analysis anomaly
-
Independence-limited stream protection
The old school district was all over the process.Not at all.。
V. The key role played by cloud deployment here
If the campus network Authentication & Billing system still remains“Single point deployment in the school”New school access is almost impossible to achieve zero impact.
The core capabilities of cloud deployment are:
-
School Area Logic Decoder
-
Flexible allocation of resources
-
Risk segregation
During the new campus's online visit:
-
Computation of resources prioritise to new campuses
-
The pool of resources used by the old campus is not being used.
-
Any anomaly can roll back at any time.
That's why.The multi-school colleges will eventually move towards a unified cloud.。
VI. NEW SCHOOL AND EVOLUTION, WHY THE OLD CHARACTER“No feeling.”
The key reasons are:
-
And then we'll split it by the campus dimensions.
-
Sessions are separated by the logic of the campus.
-
The billing engine runs according to the campus example.
At the system level, the new campus is 50,000 terminals.“Squeeze”Old school district, 50,000 terminals.
Within the campus network Authentication & Billing, they are not in the same pool.
VII. The true access of anonymous college groups
A college group, the old campus, has been running for over six years. The new campus is one-off planning 20,000 beds:
-
The old campus Authentication & Billing system remains unchanged
-
New campus independent running area access
-
The first month is only open 30% of users
Throughout the access cycle:
-
No complaints from the old campus.
-
Old user unconscious.
-
The problem of the new campus is all limited to our own campus.
Three months after the launch, the new campus was completely stabilized and gradually expanded.
VIII. Return to the product itself
A truly reliable campus network Authentication & Billing system, not“Multiple”But:
-
It's a scalable one.
-
It's controlled.
-
You can back off.
The inclusion of new campuses, while operating steadily in the old school complex, is itself a manifestation of the maturity of the system.
Manufacturers such as NatShell, often in these long-term deep-drawn campus networks“Unseen Design Point”It's a lot of time.——
Because only after experience of multiple campuses, cycles and versions will the system know where to touch and where to separate.