6 Business ID generation rules The database generally designs an automatically incremented ID as the primary key, and also designs an ID that uniquely identifies the enterprise. This is the so-called business ID (also called business key). For example, the order number for retrieving the retrieval field. Some people also use the so-called snowflake algorithm, but it is not suitable for payment scenarios. The following is the generation of a business ID of a -bit payment system as an example. It can be flexibly adjusted during actual application. Digit -8: date. You can tell at a glance what day the transaction was made through the order number.
Bit 9: Data version. Used to upgrade the document australia email list number. when the upgrade is incompatible. and services are processed using the old system, and new services are processed using the new system. Digits -: System identification code. Each domain within the payment system is assigned a section, which is then redistributed to the internal system by each domain. For example, is the acquisition core, and is the settlement core. Bits -5: Company identification bits. It is determined within each domain, for example, -5 represents payment business, payment, pre-authorization, payment request, etc.
Number 6-7: Computer classroom. For global application. Position 8-9: User branch location. Support Baiku. Positions -: User sub-positions. Support hundreds of meters. No. : Pre-production identification bit. For example, represents a pre-release environment, and represents a production environment. Positions -: Reserved. Each domain can be expanded according to actual conditions. Bits -: Serial number space. million, recycled. A single computer room can process millions of transactions per day, which is a very large volume. If that is not enough, it can be expanded to .
Digit: System version. Used for internal system version upgrades, especially
-
- Posts: 5
- Joined: Mon Dec 23, 2024 4:09 pm