CN116866304A - Ignite-based distributed number generator implementation method and system - Google Patents
Ignite-based distributed number generator implementation method and system Download PDFInfo
- Publication number
- CN116866304A CN116866304A CN202310796750.3A CN202310796750A CN116866304A CN 116866304 A CN116866304 A CN 116866304A CN 202310796750 A CN202310796750 A CN 202310796750A CN 116866304 A CN116866304 A CN 116866304A
- Authority
- CN
- China
- Prior art keywords
- ignite
- distributed
- node
- information
- sender
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 45
- 230000006870 function Effects 0.000 claims description 10
- 238000012545 processing Methods 0.000 claims description 10
- 238000004422 calculation algorithm Methods 0.000 claims description 9
- 238000004590 computer program Methods 0.000 claims description 9
- 241000533950 Leucojum Species 0.000 claims description 7
- 230000002085 persistent effect Effects 0.000 claims description 5
- 239000008186 active pharmaceutical agent Substances 0.000 description 7
- 238000010586 diagram Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 238000013480 data collection Methods 0.000 description 2
- 238000000586 desensitisation Methods 0.000 description 2
- 230000005012 migration Effects 0.000 description 2
- 238000013508 migration Methods 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/30—Managing network names, e.g. use of aliases or nicknames
- H04L61/3015—Name registration, generation or assignment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
Abstract
The application provides a distributed number sender realization method and a system based on Ignit, which are characterized by comprising the following steps: s1, performing first configuration on an Ignite node to open a REST API function of the Ignite node; s2, acquiring first request information of an application, wherein the first request comprises an HTTP request, and the first request information comprises first identification information and step length information of a sender; s3, polling and inquiring the corresponding number generator based on the first identification information of the number generator until the corresponding number generator is found, and generating a distributed serial number by the number generator according to the step size information and the initial serial number; s4, judging whether a preset condition for stopping generating the distributed serial number is met, and stopping generating the distributed serial number if the preset condition is met. The application can quickly interact with the distributed sender service constructed by the Ignite cluster only by the request of the client and acquire the distributed ID serial number with globally unique trend increment.
Description
Technical Field
The application relates to the technical field related to a distributed number sender implementation method, in particular to a distributed number sender implementation method and system based on Ignite.
Background
In distributed systems, it is often necessary to uniquely identify a large amount of data, messages, http requests, etc., such as order serial numbers, operation record serial numbers, coupon IDs, etc., and a stable ID generation service is required to generate these unique identifications. The general implementation mode has a database self-increasing primary key, and the distributed ID generation based on a snowflake algorithm and the like can meet the global uniqueness of ID serial numbers, and the trend is increased.
At present, a snowflake algorithm-based distributed ID generation mode is complex, a developer is required to consider the problems of time callback and the like, the ID generated by using a database-like self-increasing mode is enough in a general service scene, but the database has a certain performance bottleneck, and the database-like self-increasing primary key generation mode has poor performance; the user also needs to execute various SQL according to different databases to generate ID, resulting in high coupling degree and poor maintainability.
Based on the technical problems, the application provides a distributed number generator realization method and a distributed number generator realization system based on Ignit, which use a memory to store and change ID serial numbers, and compared with the method which uses a database self-increasing primary key to generate ID, the method has the advantages that the performance of generating ID is greatly improved, and the performance of acquiring ID by application can be expanded by increasing the number of nodes in an Ignit cluster. The application obtains the ID from the Ignite cluster sender in the mode of HTTP request, and is decoupled with application service logic, so that maintainability is higher. After the method and the system for realizing the number sender are used, the application can quickly interact with the distributed number sender service constructed by the Ignit cluster only through HTTP requests and acquire the distributed ID serial number with globally unique trend increment without integrating any database client and ID generation component codes.
It is worth noting that the data collection and migration actions involved in the present application are already agreed by the user and are necessary for the applicant to perform normal operation activities. The collected data applicants are subjected to desensitization treatment such as anonymization and confidentiality, and the access rights of the data are correspondingly set so as to ensure that the privacy of users cannot be revealed. The data processing activities performed by the applicant accord with the rules of laws and regulations such as data security laws and personal information protection laws.
Disclosure of Invention
Aiming at the defects of the background technology, the application provides a distributed number sender realization method and system based on Ignite. Comprising the following steps:
the first aspect of the present application proposes a method for implementing a distributed number sender based on Ignite, which is characterized by comprising:
s1, performing first configuration on an Ignite node to open a REST API function of the Ignite node;
s2, acquiring first request information of an application, wherein the first request comprises an HTTP request, and the first request information comprises first identification information and step length information of a sender;
s3, polling and inquiring the corresponding number generator based on the first identification information of the number generator until the corresponding number generator is found, and generating a distributed serial number by the number generator according to the step size information and the initial serial number;
s4, judging whether a preset condition for stopping generating the distributed serial number is met, and stopping generating the distributed serial number if the preset condition is met.
Further, the method further comprises S5: and (3) storing the distributed serial numbers in a persistent mode and/or returning the distributed serial numbers to the application.
Further, the method further includes S6:
s61, judging whether the performance of the distributed number sender meets the requirement or not based on the application requirement information;
s62, if the requirement cannot be met, adding the new Ignite node into the existing Ignite node cluster.
Further, the step size information may be preset in an Ignite node, and the first identification information of the number sender is stored in a key value pair manner, where the first identification information of the number sender is a key value.
Further, the step S3 includes:
s31, inquiring whether the sender is at an Ignite node or not based on a key value; the method comprises the steps of carrying out a first treatment on the surface of the
S32, if the first request information is not on the Ignite node, the Ignite node sends the first request information to a new Ignite node until a corresponding sender is found.
Further, the step S3 further includes:
s301, setting an initial sequence number, and determining the number of transmitters by an Ignite node cluster based on step length information;
s302, generating a distributed serial number according to a first preset rule based on the initial serial number, wherein the first preset rule comprises a splicing rule and a snowflake algorithm.
The second aspect of the present application proposes a distributed number sender implementation device based on Ignite, which is characterized in that it comprises:
the configuration module is used for carrying out first configuration on the Ignite node to open the REST API function of the Ignite node;
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring first request information of an application, the first request comprises an HTTP request, and the first request information comprises first identification information and step length information of a sender;
the query generation module is used for polling and querying the corresponding number generator based on the first identification information of the number generator until the corresponding number generator is found, and generating a distributed serial number according to the step size information and the initial serial number;
and the judging termination module is used for judging whether the preset condition for stopping generating the distributed serial number is met, and stopping generating the distributed serial number if the preset condition is met.
A third aspect of the present application proposes an electronic device, characterized by comprising: a processor, and a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes the computer-executed instructions stored in the memory to implement the method implemented by the Ignite-based distributed number generator.
A fourth aspect of the present application proposes a computer readable storage medium, wherein computer executable instructions are stored in the computer readable storage medium, and the computer executable instructions are used for implementing the method implemented by the Ignite-based distributed number generator when being executed by a processor.
A fifth aspect of the present application proposes a computer program product comprising a computer program which, when executed by a processor, implements the method implemented by an Ignite-based distributed number generator as described above.
The beneficial effects of the application are as follows: the memory stores and changes the ID sequence number, compared with the performance of generating the ID by using the database self-increasing primary key, the performance of acquiring the ID by the application can be expanded by increasing the number of nodes in the Ignite cluster. The application obtains the ID from the Ignite cluster sender in the mode of HTTP request, and is decoupled with application service logic, so that maintainability is higher. After the method and the system for realizing the number sender are used, the application can quickly interact with the distributed number sender service constructed by the Ignit cluster only through HTTP requests and acquire the distributed ID with globally unique trend increment without integrating any database client and ID generation component codes.
Drawings
Fig. 1 is a flow chart of the implementation method of the Ignite-based distributed number generator.
Fig. 2 is a block diagram of the implementation device of the distributed number generator based on Ignite.
Fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
For a clearer understanding of the present application, reference will be made to the following detailed description taken in conjunction with the accompanying drawings and examples.
It should be understood that the description is only illustrative and is not intended to limit the scope of the application. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the present application. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The words "a", "an", and "the" as used herein are also intended to include the meaning of "a plurality", etc., unless the context clearly indicates otherwise. Furthermore, the terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner. The present application is an improvement of the prior art, and therefore, the undescribed portions of the application are implemented in the prior art.
At present, a snowflake algorithm-based distributed ID generation mode is complex, a developer is required to consider the problems of time callback and the like, the ID generated by using a database-like self-increasing mode is enough in a general service scene, but the database has a certain performance bottleneck, and the database-like self-increasing primary key generation mode has poor performance; the user also needs to execute various SQL according to different databases to generate ID, resulting in high coupling degree and poor maintainability.
Based on the technical problems, the application provides a distributed number sender implementation method and system based on Ignit. The Ignite database has Elasticity, i.e. the advantage that clusters can be horizontally expanded by adding nodes, distributed computing, and the apache Ignite provides a set of simple APIs that allow users to obtain high performance distributed computing and data processing capabilities on multiple nodes. The distributed services of ignit also provide a lot of assistance in developing and executing micro-service architecture. Compared with the performance of generating the ID by using the database self-increasing primary key, the performance of acquiring the ID by the application can be expanded by increasing the number of nodes in the Ignite cluster due to the elasticity of Ignite nodes. After the application is applied, the application obtains the ID from the Ignite cluster sender in a request mode, and is decoupled with the application service logic, so that the maintainability is higher. After the method and the system for realizing the number sender are used, the application can quickly interact with the distributed number sender service constructed by the Ignit cluster only through HTTP requests and acquire the distributed ID serial number with globally unique trend increment without integrating any database client and ID generation component codes.
Fig. 1 is a flow chart of the implementation method of the Ignite-based distributed number generator. The first aspect of the present application proposes a method for implementing a distributed number sender based on Ignite, which is characterized by comprising:
s1, performing first configuration on an Ignite node to open a REST API function of the Ignite node;
specifically, starting up multiple ignit nodes, the nodes need to start up the functions provided by REST API, i.e. the ignit-REST-http module needs to be copied from { ignite_home }/libs/optional/to { ignite_home }/libs, { ignite_home } is the root directory of ignit, so as to be able to accept due requests and the information carried by the requests. The storage function of the Ignite node can be started in the link, specifically, the starting persistence is configured in the data area, so as to prevent the loss of the data of the holding ID serial number after the Ignite node is down, and then a plurality of nodes form an Ignite cluster.
S2, acquiring first request information of an application, wherein the first request comprises an HTTP request, and the first request information comprises first identification information and step length information of a sender;
specifically, because the Ignite node is configured, the application may directly send a request to the Ignite node, and the Ignite node may perform a parsing operation on the request of the application.
Preferably, the application sends out an HTTP request, and requests a sender to acquire the ID sequence number randomly or in a specified manner, and the first request information contains step information, for example: http:// ip address: port/ignitechd=incr & key=idgenmachine 001& delta=10, where the identification key of the sender is IDGenMachine001, the identification of the sender can be stored in a key-value pair manner, and when the Ignite node receives an HTTP request, the sender can be queried according to the identification. Delta is the step size information, 10 is set here, in the application, the step size and the identification information of the number sender are always required to be set, if the Ignite node or the HTTP request has default setting, the corresponding step size information and the identification information of the number sender can be changed in the HTTP request.
Specifically, the first request information may further include an incr command, which is used to start an incr command provided in the Ignite REST API of the Ignite node, and initialize a number sender in the Ignite cluster.
S3, polling and inquiring the corresponding number generator based on the first identification information of the number generator until the corresponding number generator is found, and generating a distributed serial number by the number generator according to the step size information and the initial serial number;
further, the step S3 includes:
s31, inquiring whether the sender is at an Ignite node or not based on a key value; the method comprises the steps of carrying out a first treatment on the surface of the
S32, if the first request information is not on the Ignite node, the Ignite node sends the first request information to a new Ignite node until a corresponding sender is found.
Further, the step S3 further includes:
s301, setting an initial sequence number, and determining the number of transmitters by an Ignite node cluster based on step length information;
s302, generating a distributed serial number according to a first preset rule based on the initial serial number, wherein the first preset rule comprises a splicing rule and a snowflake algorithm.
Specifically, the load balancing device arranged in front of the Ignite cluster node can query the HTTP request in the application for the number sender according to the identification information of the number sender, and the Ignite node judges whether the sub number sender of the request is on the node according to the key value content (namely the identification of the number sender) in the HTTP request. If the node is in the node, a distributed serial number (distributed ID, distributed serial number, distributed ID serial number are the same object) can be generated according to a preset rule, the preset rule can be an algorithm, or each component of the serial number can be spliced together, for example, a timestamp is spliced together with the serial number, or other calculation rules can be used for guaranteeing that the final distributed ID is unique, for example, delta step information in an http request is added with an initial serial number of the sender to obtain a next serial number which can be supported by the sub sender, if a new serial number needs to be obtained, the serial number subjected to the first step adding is taken as the initial serial number, and a step is added to obtain a new serial number, for example:
number sender 1: the KEY value is "IDGenMachine001", the initialization ID sequence number is 1, the prescribed step length is 10, and the generated ID sequences are 11, 21, 31 and 31 …
After the current IDs are added, the ID serial number of the sender can be updated and then returned to the application;
if the node is not located on the node, the node where the Ignit node is located is found according to the key value in the http request, the node will transmit the delta step length in the http request to the node where the child sender is located, the node where the child sender is located will obtain a new serial number in the same updating mode as the updating logic of the node), the ID serial number is returned to the node, and the node replies the application request.
S4, judging whether a preset condition for stopping generating the distributed serial number is met, and stopping generating the distributed serial number if the preset condition is met.
Further, the method further comprises S5: and (3) storing the distributed serial numbers in a persistent mode and/or returning the distributed serial numbers to the application.
Specifically, the application does not limit the storage mode, the purpose of persistent storage is to prevent the loss of the data of the serial number of the holding ID after the Ignit node is down, and the purpose of generating the distributed ID is to be returned to the application.
Further, the method further includes S6:
s61, judging whether the performance of the distributed number sender meets the requirement or not based on the application requirement information;
s62, if the requirement cannot be met, adding the new Ignite node into the existing Ignite node cluster.
Specifically, due to elasticity of the Ignite, when performance of the distributed number sender constructed by the Ignite cluster cannot meet application requirements, the Ignite node is directly started to join the cluster, and the Ignite can automatically and evenly distribute the sub number sender in nodes of the whole cluster.
Further, the step size information may be preset in an Ignite node, and the first identification information of the number sender is stored in a key value pair manner, where the first identification information of the number sender is a key value.
The step size information can be preset in the Ignite node, the setting mode is default, for example, 10, and the step size information can also be obtained from the request.
Fig. 2 is a block diagram of the implementation device of the distributed number generator based on Ignite. The second aspect of the present application proposes a distributed number sender implementation device based on Ignite, which is characterized in that it comprises:
the configuration module is used for carrying out first configuration on the Ignite node to open the REST API function of the Ignite node;
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring first request information of an application, the first request comprises an HTTP request, and the first request information comprises first identification information and step length information of a sender;
the query generation module is used for polling and querying the corresponding number generator based on the first identification information of the number generator until the corresponding number generator is found, and generating a distributed serial number according to the step size information and the initial serial number;
and the judging termination module is used for judging whether the preset condition for stopping generating the distributed serial number is met, and stopping generating the distributed serial number if the preset condition is met.
Further, the device further includes a storage module and/or a return module for S5: and (3) storing the distributed serial numbers in a persistent mode and/or returning the distributed serial numbers to the application.
Further, the device further includes a new module, configured to S6:
s61, judging whether the performance of the distributed number sender meets the requirement or not based on the application requirement information;
s62, if the requirement cannot be met, adding the new Ignite node into the existing Ignite node cluster.
Further, the device further comprises a preset module, wherein the preset module is used for presetting step length information on the Ignite node, and the first identification information of the number sender is stored in a key value pair mode, wherein the first identification information of the number sender is a key value.
Further, the query generation module is configured to:
s31, inquiring whether the sender is at an Ignite node or not based on a key value; the method comprises the steps of carrying out a first treatment on the surface of the
S32, if the first request information is not on the Ignite node, the Ignite node sends the first request information to a new Ignite node until a corresponding sender is found.
Further, the query generation module is further configured to:
s301, setting an initial sequence number, and determining the number of transmitters by an Ignite node cluster based on step length information;
s302, generating a distributed serial number according to a first preset rule based on the initial serial number, wherein the first preset rule comprises a splicing rule and a snowflake algorithm.
Fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 3, the electronic device may include: a transceiver 121, a processor 122, a memory 123.
Processor 122 executes the computer-executable instructions stored in the memory, causing processor 122 to perform the aspects of the embodiments described above. The processor 122 may be a general-purpose processor including a central processing unit CPU, a network processor (network processor, NP), etc.; but may also be a digital signal processor DSP, an application specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component.
Memory 123 is coupled to processor 122 via the system bus and communicates with each other, and memory 123 is configured to store computer program instructions.
The transceiver 121 may be configured to obtain first request information of an application, where the first request includes an HTTP request, and the first request information includes first identification information of a sender and step size information.
The system bus may be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA) bus, among others. The system bus may be classified into an address bus, a data bus, a control bus, and the like. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus. The transceiver is used to enable communication between the database access device and other computers (e.g., clients, read-write libraries, and read-only libraries). The memory may include random access memory (random access memory, RAM) and may also include non-volatile memory (non-volatile memory).
The electronic device provided by the embodiment of the application can be the terminal device of the embodiment.
The embodiment of the application also provides a chip for running the instruction, which is used for executing the technical scheme of the method for realizing the distributed number sender based on the Ignit in the embodiment.
The embodiment of the application also provides a computer readable storage medium, wherein the computer readable storage medium stores computer instructions, and when the computer instructions run on a computer, the computer is caused to execute the technical scheme of the method realized by the Ignit-based distributed number sender in the embodiment.
The embodiment of the application also provides a computer program product, which comprises a computer program stored in a computer readable storage medium, the computer program can be read from the computer readable storage medium by at least one processor, and the technical scheme of the method implemented by the Ignite-based distributed number sender in the embodiment can be realized when the computer program is executed by the at least one processor.
The beneficial effects of the application are as follows: compared with the performance of using a database self-increasing primary key to generate the ID, the performance of the Ignit for acquiring the ID by the application can be greatly improved by storing and changing the ID sequence number through the memory, and the number of nodes in the Ignit cluster can be increased. The application obtains the ID from the Ignite cluster sender in the mode of HTTP request, and is decoupled with application service logic, so that maintainability is higher. After the method and the system for realizing the number sender are used, the application can quickly interact with the distributed number sender service constructed by the Ignit cluster only through HTTP requests and acquire the distributed ID with globally unique trend increment without integrating any database client and ID generation component codes.
It is worth noting that the data collection and migration actions involved in the present application are already agreed by the user and are necessary for the applicant to perform normal operation activities. The collected data applicants are subjected to desensitization treatment such as anonymization and confidentiality, and the access rights of the data are correspondingly set so as to ensure that the privacy of users cannot be revealed. The data processing activities performed by the applicant accord with the rules of laws and regulations such as data security laws and personal information protection laws.
Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.
Those skilled in the art will further appreciate that the algorithm steps described in connection with the embodiments disclosed herein are capable of being carried out in electronic hardware, computer software, or a combination of both, and that the functions are carried out in either hardware or software, depending on the particular application and design constraints of the solution, those skilled in the art can utilize different methods for achieving the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.
While preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the application.
The foregoing is only a preferred embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions easily contemplated by those skilled in the art within the scope of the present application should be included in the scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.
Claims (10)
1. The implementation method of the distributed number generator based on the Ignit is characterized by comprising the following steps of:
s1, performing first configuration on an Ignite node to open a REST API function of the Ignite node;
s2, acquiring first request information of an application, wherein the first request comprises an HTTP request, and the first request information comprises first identification information and step length information of a sender;
s3, polling and inquiring the corresponding number generator based on the first identification information of the number generator until the corresponding number generator is found, and generating a distributed serial number by the number generator according to the step size information and the initial serial number;
s4, judging whether a preset condition for stopping generating the distributed serial number is met, and stopping generating the distributed serial number if the preset condition is met.
2. The method according to claim 1, characterized in that the method further comprises S5: and (3) storing the distributed serial numbers in a persistent mode and/or returning the distributed serial numbers to the application.
3. The method according to claim 1, characterized in that the method further comprises S6:
s61, judging whether the performance of the distributed number sender meets the requirement or not based on the application requirement information;
s62, if the requirement cannot be met, adding the new Ignite node into the existing Ignite node cluster.
4. The method of claim 1, wherein the step size information is further preset in an Ignite node, and the first identification information of the number generator is stored in a key value pair manner, wherein the first identification information of the number generator is a key value.
5. The method of claim 4, wherein S3 comprises:
s31, inquiring whether the sender is at an Ignite node or not based on a key value; the method comprises the steps of carrying out a first treatment on the surface of the
S32, if the first request information is not on the Ignite node, the Ignite node sends the first request information to a new Ignite node until a corresponding sender is found.
6. The method of claim 1, wherein S3 further comprises:
s301, setting an initial sequence number, and determining the number of transmitters by an Ignite node cluster based on step length information;
s302, generating a distributed serial number according to a first preset rule based on the initial serial number, wherein the first preset rule comprises a splicing rule and a snowflake algorithm.
7. An Ignite-based distributed number generator implementation device, which is characterized by comprising:
the configuration module is used for carrying out first configuration on the Ignite node to open the REST API function of the Ignite node;
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring first request information of an application, the first request comprises an HTTP request, and the first request information comprises first identification information and step length information of a sender;
the query generation module is used for polling and querying the corresponding number generator based on the first identification information of the number generator until the corresponding number generator is found, and generating a distributed serial number according to the step size information and the initial serial number;
and the judging termination module is used for judging whether the preset condition for stopping generating the distributed serial number is met, and stopping generating the distributed serial number if the preset condition is met.
8. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored in the memory to implement the method of any one of claims 1-6.
9. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out the method of any one of claims 1-6.
10. A computer program product comprising a computer program which, when executed by a processor, implements the method of any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310796750.3A CN116866304A (en) | 2023-06-30 | 2023-06-30 | Ignite-based distributed number generator implementation method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310796750.3A CN116866304A (en) | 2023-06-30 | 2023-06-30 | Ignite-based distributed number generator implementation method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116866304A true CN116866304A (en) | 2023-10-10 |
Family
ID=88233367
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310796750.3A Pending CN116866304A (en) | 2023-06-30 | 2023-06-30 | Ignite-based distributed number generator implementation method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116866304A (en) |
-
2023
- 2023-06-30 CN CN202310796750.3A patent/CN116866304A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110049087B (en) | Credibility verification method, system, device and equipment of alliance chain | |
| EP3817333B1 (en) | Method and system for processing requests in a consortium blockchain | |
| CN111460458B (en) | Data processing method, related device and computer storage medium | |
| CN109885786B (en) | Data caching processing method and device, electronic equipment and readable storage medium | |
| CN110046901B (en) | Credibility verification method, system, device and equipment of alliance chain | |
| CN110661658A (en) | Node management method and device of block chain network and computer storage medium | |
| CN113810465B (en) | Asynchronous binary consensus method and device | |
| CN110597918A (en) | Account management method and device and computer readable storage medium | |
| CN111367672A (en) | Data caching method and device, electronic equipment and computer storage medium | |
| CN111694639B (en) | Updating method and device of process container address and electronic equipment | |
| CN112069169A (en) | Block data storage method and device, electronic equipment and readable storage medium | |
| CN108154024B (en) | Data retrieval method and device and electronic equipment | |
| CN110764688A (en) | Method and device for processing data | |
| CN113794576B (en) | Re-voting binary consensus method and device | |
| CN116866304A (en) | Ignite-based distributed number generator implementation method and system | |
| CN111092958A (en) | Node access method, device, system and storage medium | |
| CN113746918A (en) | Hypertext transfer protocol proxy method and system | |
| CN112637106B (en) | Method and device for terminal to access website | |
| CN113726885A (en) | Method and device for adjusting flow quota | |
| CN112688870A (en) | Routing method, routing device and node equipment | |
| CN111382200A (en) | Information loading method and device, server and storage medium | |
| CN116305288B (en) | Method, device, equipment and storage medium for isolating database resources | |
| CN110889040B (en) | Method and device for pushing information | |
| CN110830510B (en) | Method, device, equipment and storage medium for detecting DOS attack | |
| CN117883789B (en) | Data acquisition method, apparatus, device, readable storage medium, and program product |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |