The Portal billing project is not going to be a question: whether certification and billing are one or two systems. Many manufacturers have implicitly integrated, many customers fear being tied up. There is no standard answer. It is important to see who changes the rules, changes in frequency, and whether they share the same calibre. Think about organization rather than architecture, the answers are naturally clear, and do not get beat by the default options of the manufacturer.
Integration is a place where rules rarely change.
If the certification and billing are managed by the same person, it is not done six months a year, the account number is single, and integration is most economical. A system, a set of accounts, one login, online quick, and less point of delivery. The simpleness of integration in small places, single shops, is an advantage, and there is no need to divide them into two. Integration has the hidden benefit: authentication and billing meetings are naturally identical, do not connect without matching, and the output caliber is not incompatible. For such scenarios, breaking down is more than just self-help and requires an interface.
Splitting is for each side to evolve.
The combination of multiple identification sources, and frequent transfer of fees and policies on the side of the billing process. Certification upgrades are subject to cost distribution, fee-reform rules are configured for certification, and the iterative rhythm is locked down. This time, the authentication platform, billing engine, intermediate event and standard interfaces are open and each evolves. The interface moves with the other.
Connecting by session identification is not time-synchronous
Whether it is broken, the time-to-charge process must start to run on the same chain. The delay becomes a reconciliation gap by a few minutes with a timed task to brush data. The correct approach is to certify that a live billing of an uplink event has been successfully carried out and the billing is done. The meeting signs are shared, and the drifting line is matched by the same account, which is the nature of the connection and does not matter for the system to merge. The session markers are best time stamped and sourced to facilitate subsequent retrace of who, from where and when the top line is, audit and access barriers depend on it, not an optional field.
Whoever changes the rules, he's got to take his caliber.
The splitting or matching of rules depends on who is making the daily configuration. If the billing rules are changed frequently by finance or operation, certified by network management, and combined, each change in charge of a fee is triggered by an error of certification, authority and responsibility is confused. By reducing the changes to one side, system patterns follow. Clear accountability affects day-to-day stability and instability more than architecture.
Integration has hidden locking costs.
Integration saves the docking, but it is tied deep. The price increases for manufacturers are hard to change and function at an iterative rate with the manufacturer. To be able to identify costs, there are alternatives to key functions, and data can be exported in full. Don't save on the connection fees, give lifelines to one, or you can lose your body when prices rise or stop.
Disconnected interface governance cannot be avoided
Breaking up is the key to the interface. There are rules for the interface version, field changes, back-to-back compatibility. One party changes without notice, and the other party makes a mistake. The interface is well managed, splits are free; it is not good enough to do so, because errors are hidden in invisible fields. The interface has to be led by a change review, there is a regression, and one missing, and the split will soon fall apart.
How do you share the session status?
Whether they are broken down, the conversation state needs a single storage, authentication, and billing. It cannot be stored separately. Sharing the memory is reliable. Don't use local memory. No reboot.
We need to get back on the ground.
The rules are charged to the charge today, and tomorrow they will be operational, and the system will support a change of authority and responsibility. The configuration and separation of powers, with the replacements merely changing the authorization, does not alter the structure. Flexible organizational alignment is more resistant than fixed structures, business changes do not have to rewrite the system, and implementation costs are much lower.
First, we'll have to make a long-term architecture.
The breakup is a lockdown, and the first one is a hard-core operation, observing who is changing rules, how often they are changed, and how long-term patterns are defined. Premature structure, often mismatched with real tissue rhythms, is more expensive to get back to work than later.
Don't use technology to make business decisions.
It is not important to take a break back to who changed the rules and how often the tides were. The team was more messy than it was when it broke down, and then decided to set the pace of business, which was not brought into the architecture, so that the system would serve rather than the system.
Portal's billing and certification are still going to be done, not technically selected, but organized. The rules are changed, changed frequently, whether or not the same calibre is needed. Three questions come out, naturally. Don't let the manufacturer get away with integrated speech, or split it for split purposes.