WO2017012492A1 - 表单标示符生成方法、表单分流方法和装置 - Google Patents

表单标示符生成方法、表单分流方法和装置 Download PDF

Info

Publication number
WO2017012492A1
WO2017012492A1 PCT/CN2016/089867 CN2016089867W WO2017012492A1 WO 2017012492 A1 WO2017012492 A1 WO 2017012492A1 CN 2016089867 W CN2016089867 W CN 2016089867W WO 2017012492 A1 WO2017012492 A1 WO 2017012492A1
Authority
WO
WIPO (PCT)
Prior art keywords
identifier
generating
routing
sub
bit
Prior art date
Application number
PCT/CN2016/089867
Other languages
English (en)
French (fr)
Inventor
熊中根
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2017012492A1 publication Critical patent/WO2017012492A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/40—Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
    • G06F16/43—Querying

Definitions

  • the present application relates to the field of database technologies, and in particular, to a form identifier generation method, a form distribution method, a form identifier generation device, and a form flow distribution device.
  • An ID is an identifier that uniquely identifies one of the objects within a search domain.
  • the auto_increment attribute or sequence object is generally used as a method of generating an ID to uniquely mark a record. This method can ensure the uniqueness of the ID in the single-library mode.
  • the system scale is expanded and the single-library single-table cannot meet the growth requirements of the business data, it is necessary to carry out the expansion and transformation of the sub-library table.
  • Each sub-library form also needs to generate a global unique identification code ID.
  • a UUID is generated by using various algorithms according to parameters such as a MAC address and a clock of a current computer, but the ID generated by the method has no service level.
  • Information such as date and time information; and MongoDB Object ID generated based on a combination of timestamp, MAC address, current process, etc., although the generation method can form a unique ID according to the multi-part information, but the information contained therein is applied to the application service.
  • the layer is transparent, and the application business layer cannot perceive and utilize this information.
  • the technical problem to be solved by the embodiment of the present application is to provide a form identifier generation method and a form distribution method, which can facilitate the form flow off operation of the application service layer.
  • the embodiment of the present application further provides a form identifier generating device and a form shunt device for ensuring implementation and application of the above method.
  • the present application discloses a method for generating a form identifier, including:
  • Generating a unique identifier portion and a route indication portion including: generating the route indication portion according to a preset form flow routing rule;
  • the generating the routing indication part according to the preset form offload routing rule includes:
  • the generating the routing indication part according to the preset form flow routing rule further includes:
  • the sub-table flag is generated according to the preset form table routing rule.
  • branch identifier bit and the part table identifier bit each include at least 2 characters.
  • the generating the routing indication part according to the preset form offload routing rule includes:
  • a feature bit is selected in the user identifier as the route indication portion.
  • the generating a unique identifier portion includes:
  • generating the first indication part according to the associated parameter of the application corresponding to the form including:
  • the embodiment of the present application further discloses a form shunting method, including:
  • the form is shunted according to the routing indication portion of the form.
  • the offloading the form according to the routing indication part of the form includes:
  • the form is offloaded to a table set corresponding to the part indicator bits in the database.
  • the embodiment of the present application further discloses a form identifier generating device, including:
  • a first label generating unit configured to generate a unique label portion
  • a second label generating unit configured to generate the route labeling part according to a preset form shunt routing rule
  • the combination generating unit is configured to generate an identifier of the form according to the unique identifier portion and the route label portion combination.
  • the second indicator generating unit is configured to generate a library according to a preset form library routing rule Mark the bit.
  • the second indicator generating unit is further configured to generate a part table identifier according to the preset form table routing rule.
  • the embodiment of the present application further discloses a form flow dividing device, including:
  • a receiving unit configured to receive a form of gateway shunting, wherein the identifier of the form is generated according to the foregoing method
  • An obtaining unit configured to obtain an identifier of the form
  • a reading unit configured to read a route indication portion in the form identifier
  • the offloading unit is configured to offload the form according to the routing indication portion of the form.
  • the shunting unit includes:
  • a sub-library unit configured to offload the form to a database corresponding to the sub-library flag according to the sub-package flag bit included in the route indication portion;
  • the sub-table sub-unit is configured to offload the form to a table set corresponding to the sub-table identifier bit in the database according to the sub-table flag bit included in the route indication part.
  • the embodiments of the present application include the following advantages:
  • the unique identifier of the form is generated by using the unique labeling part and the form shunt routing rule, so that the application service layer can perceive and utilize the information to perform form splitting, and in particular, the route marking part in the identifier can be used according to the predetermined Form shunt routing rules for form shunting.
  • the method for generating the unique identifier of the form can not only satisfy the uniqueness of the global ID of the technical level, but also facilitate the application layer to perform the form shunting operation by using the routing information contained in the form identifier in the sub-database sub-table environment.
  • the splitting of the sub-library tables of large-scale massive data in the environment provides good scalability and routing rules.
  • FIG. 1 is a flow chart showing the steps of an embodiment of a method for generating a form identifier of the present application
  • FIG. 2 is a flow chart showing the steps of an embodiment of a method for generating a first indication portion of the present application
  • FIG. 3 is a flow chart showing the steps of an embodiment of a method for generating a route indication portion of the present application
  • FIG. 4 is a schematic structural diagram of a form identifier of the present application.
  • FIG. 5 is a flow chart of steps of an embodiment of a form shunting method of the present application.
  • FIG. 6 is a flow chart of steps of an embodiment of a method for offloading a form according to a route marking portion of a form according to the present application;
  • FIG. 7 is a structural block diagram of an embodiment of a form identifier device of the present application.
  • FIG. 8 is a structural block diagram of an embodiment of a form shunting device of the present application.
  • FIG. 9 is a structural block diagram of an embodiment of a shunt unit of the present application.
  • FIG. 1 a flow chart of steps of a method for generating a form identifier of the present application is shown, which may specifically include the following steps:
  • step 101 a unique identifier portion and a route indication portion are generated.
  • the device for generating a unique identifier of the form first generates each part constituting the identifier, including generating a unique label portion and a route label portion, wherein the unique label portion may include the first label portion and serial number.
  • the first indication part is generated according to the associated parameter of the application corresponding to the form;
  • the route indication part is generated according to the preset form flow distribution routing rule;
  • the serial number of the form is obtained according to the generated sequence of the form.
  • the generation of each part can be performed sequentially or simultaneously, and the order is not limited.
  • the first indicator part may be generated according to the startup parameter of the application, and may include date information, version information, service information, and the like.
  • the route labeling part is generated according to the routing rule when the form is split according to a preset form.
  • the form flow distribution routing rule is to divide the form of the same user into the same database, and the generated route marking part needs to include the user identification information.
  • the predetermined routing rule can be implemented according to the route marking part.
  • the routing indication part may only include the sub-library indication bit. If the diversion of the form is to perform the sub-database sub-table, the routing indication part may include the sub-library indication bit and the sub-table indication bit.
  • the serial number of the form is also the serial number generated by the form. In order to support a sufficient amount of data, the serial number can be set to 8 bits.
  • Step 102 Generate an identifier of the form according to the combination of the unique indication part and the route indication part.
  • the step may be combined to generate a unique identifier of the form according to a certain order or rule, for example, the first indication part, the route indication part and the serial number are sequentially spliced in Together, you can generate a unique identifier for the form.
  • the embodiment of the present application generates by using the associated parameters of the application, the form shunt routing rule, and the serial number of the form.
  • the unique identifier of the form enables the application business layer to perceive and utilize the information for form shunting, and in particular, the route labeling part in the identifier can be used to perform form shunting according to the predetermined form shunt routing rule.
  • the method for generating the unique identifier of the form can not only satisfy the uniqueness of the global ID of the technical level, but also facilitate the application layer to perform the form shunting operation by using the routing information contained in the form identifier in the sub-database sub-table environment.
  • the splitting of the sub-library tables of large-scale massive data in the environment provides good scalability and routing rules.
  • the device generates a first labeling portion according to the associated parameter of the application corresponding to the form.
  • the method may include:
  • Step 201 Generate a date flag according to the date of the application service.
  • the device can obtain the date of the current application service and intercept the 8-digit year, month, and day string as the date indicator.
  • Step 202 Generate a data version bit, a system version bit, a system flag bit, and a service flag bit according to the startup parameter of the application.
  • the device can configure the data version bit and the system version bit according to the startup parameter configuration of the application, wherein the data version bit and the system version bit can both be 1 bit.
  • the device can set a 3-digit system flag according to the application startup parameter, which is used to indicate which application in the cluster is generated by the application in the cluster;
  • the device sets a 3-bit service indicator bit according to the application startup parameter, and is used to indicate what service the data associated with the form identifier is.
  • the device generates a route labeling part according to a preset form flow routing rule, as shown in FIG. 3, which may include:
  • Step 301 Generate a library identifier bit according to a preset form sub-database routing rule.
  • the device can generate a branch identifier bit in the form identifier according to a routing rule to be followed when the library is to be followed.
  • the routing rule to be followed when the library is divided is that the form of the same user is diverted to the same database, and the feature bits in the user identification information, such as uid (userId), such as the first and second digits of the last number, may be extracted.
  • uid userId
  • the library flag can have two bits to support the expansion of 100 physical libraries.
  • step 302 can also be performed.
  • Step 302 Generate a sub-table flag according to a preset form table routing rule.
  • the device can generate the sub-table identifier bit in the form identifier according to the routing rule to be followed when the table is divided.
  • the routing rule to be followed when sub-tables is that the same user's form is diverted to the same set of tables in the same database.
  • Other feature bits may be extracted from the user's identification information, such as uid (userId), such as the third and fourth digits of the last digit, as the sub-table identifier bits in the form identifier.
  • the sub-table flag can also have two bits to support the expansion of 100 sub-tables.
  • the number of bits in the library and the number of points in the table can be determined according to the number of physical libraries and table sets required.
  • the date identifier bit generated according to the date of the application service is 20141212; the data version bit, the system version bit, the system flag bit, and the service flag bit generated according to the startup parameter of the application are sequentially It is 0,1,001,001; in the online transaction payment system, because it is based on the business operation of the user login, the device can select the agreed number according to the uid (userId) as the sub-library and the sub-table indication bit.
  • the nextValue is obtained from the sequence as the serial number in the form identifier.
  • the serial number is 8 digits, and the number of digits is not enough.
  • the padding is filled with 0, assuming that the obtained serial number is 28945699.
  • the form identifier can be sorted according to the first 8 digits date + serial number; a single table can support enough data volume, the last 8 digits can have up to 100 million data records per day; the library identifier can support 100 physical libraries. Extension; the sub-table flag can support the expansion of 100 sub-tables.
  • the form corresponding to each business data will be explicitly with the user uid information, so the same user's form will fall into the same sub-library table, which is conducive to data aggregation.
  • the business application layer can easily make the sub-library table of the form and the migration cost is small, which brings a very good foundation for the data architecture layer of the entire business, and the business data is also provided. Can have good scalability.
  • FIG. 5 a flow chart of steps of an embodiment of a method for splitting a form of the present application is shown, which may specifically include the following steps:
  • Step 501 Receive a form of gateway offloading.
  • the form offloading device may specifically be an application server or the like.
  • the identifier of the form can be generated according to the method of the foregoing embodiment.
  • the form identifier includes a first indication part generated according to an associated parameter of the application corresponding to the form; a route indication part generated according to a preset form flow distribution routing rule; and a serial number of the form obtained according to the generation sequence of the form.
  • Step 502 Obtain an identifier of the form.
  • Step 503 reading the route indication part in the form identifier.
  • the route labeling part of the form identifier contains the shunt routing rules of the form.
  • step 504 the form is shunted according to the routing indication part of the form.
  • the form shunting device can perform form shunting according to the information contained in the routing indication part, and the shunting result obtained thereby can reflect the predetermined shunt routing rule.
  • the embodiment of the present application can easily perform the sub-library sub-table of the form by using the routing information contained in the form identifier, and the migration cost is small, which brings the data architecture layer of the entire service very much.
  • a good foundation, business data landing can also have good scalability.
  • the process of the form shunting device offloading the form according to the routing indication part of the form, as shown in FIG. 6, may include:
  • Step 601 The form is offloaded to a database corresponding to the branch identifier bit according to the branch identifier bit included in the route indication portion.
  • the route identifier part of the form identifier includes a branch identifier bit and a sub-table flag bit.
  • the form identifier is 2014121201001001581228945699
  • the branch identifier bit is 12
  • the sub-table flag bit is 58. This step forms the form. The flow is branched into the database 12.
  • Step 602 Divide the form into a table set corresponding to the sub-table identifier bit according to the sub-table identifier bit included in the route indication part.
  • This step continues to offload the form to the table set corresponding to the sub-table flag bit 58 in the database 12.
  • FIG. 7 a structural block diagram of an embodiment of a form identifier device of the present application is shown, which may specifically include the following units:
  • the first indicator generating unit 701 is configured to generate a unique labeling portion.
  • the second indicator generating unit 702 is configured to generate the route labeling part according to a preset form split routing rule.
  • the combination generation unit 703 is configured to generate an identifier of the form according to the combination of the unique indication portion and the route indication portion.
  • the device generates a unique identifier of the form by using the associated parameters of the application, the form shunt routing rule, and the serial number of the form, so that the application service layer can perceive and utilize the information for form shunting, and in particular, the routing indication part in the identifier can be utilized.
  • the form is shunted according to the predetermined form shunt routing rules.
  • the device for generating the unique identifier of the form can not only satisfy the uniqueness of the global ID of the technical level, but also facilitate the application layer to perform the form shunting operation by using the routing information contained in the form identifier in the sub-division table environment.
  • the splitting of the sub-library tables of large-scale massive data in the environment provides good scalability and routing rules.
  • the second indicator generating unit 702 may be configured to generate a library identifier bit according to a preset form library routing rule; or may be configured to generate a part table according to a preset form table routing rule. Mark the bit.
  • the second indicator generating unit 702 may be specifically configured to select a feature bit as the route identifier portion in the user identifier.
  • the sub-library flag and the sub-labeling bit all include at least 2 characters, and the serial number includes at least 8 characters.
  • the first indicator generating unit 701 may be configured to generate a first identifier portion according to an association parameter of the application corresponding to the form, and generate a sequence number of the form according to the generated sequence of the form.
  • the first generation subunit is configured to generate a date indication bit according to a date of the application service.
  • the second generation subunit is configured to generate a data version bit, a system version bit, a system flag bit, and a service flag bit according to the startup parameter of the application.
  • the third generation subunit is configured to generate a serial number of the form according to the generated sequence of the form.
  • the date identifier bit, the data version bit, the system version bit, the system flag bit, and the service flag bit generated by the first generation sub-unit and the second generation sub-unit are used as the foregoing first indication part.
  • the third generation subunit generates the serial number of the form.
  • FIG. 8 a structural block diagram of an embodiment of a form shunting apparatus of the present application is shown, which may specifically include the following units:
  • the receiving unit 801 is configured to receive a form of gateway offloading.
  • the obtaining unit 802 is configured to acquire an identifier of the form.
  • the reading unit 803 is configured to read a route indication portion in the form identifier.
  • the distribution unit 804 is configured to offload the form according to the routing indication portion of the form.
  • the device can easily perform the sub-library table of the form and the migration cost is small by using the routing information contained in the form identifier in the environment of the sub-division table, which brings a very good data architecture layer of the whole service.
  • Basic, business data landing can also have good scalability.
  • the shunting unit 804 may further include:
  • the sub-library subunit 901 is configured to offload the form to a database corresponding to the sub-library flag according to the sub-package flag bits included in the route indication portion.
  • the sub-table sub-unit 902 is configured to offload the form to a table set corresponding to the sub-table identifier bit in the database according to the sub-table flag bit included in the route indication part.
  • the embodiment of the present application further provides a server, including a memory and a processor.
  • the processor and the memory are connected to each other through a bus; the bus may be an ISA bus, a PCI bus, or an EISA bus.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like.
  • the memory is used to store a program, and specifically, the program may include program code, and the program code includes computer operation instructions.
  • the memory may include a high speed RAM memory and may also include a non-volatile memory such as at least one disk memory.
  • the processor is used to read the program code in the memory and perform the following steps:
  • Generating a unique identifier portion and a route indication portion including: generating the route indication portion according to a preset form flow routing rule;
  • the embodiment of the present application further provides a server, including a memory, a transceiver, and a processor.
  • the processor and the memory and the transceiver are connected to each other through a bus; the bus may be an ISA bus, a PCI bus or an EISA bus.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like.
  • the memory is used to store a program, and specifically, the program may include program code, and the program code includes computer operation instructions.
  • the memory may include a high speed RAM memory and may also include a non-volatile memory such as at least one disk memory.
  • the transceiver is used to receive the form of the gateway offload.
  • the processor is used to read the program code in the memory and perform the following steps:
  • the form is shunted according to the routing indication portion of the form.
  • the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.
  • embodiments of the embodiments of the present application can be provided as a method, apparatus, or computer program product. Therefore, the embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Moreover, embodiments of the present application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • the memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory.
  • RAM random access memory
  • ROM read only memory
  • Memory is an example of a computer readable medium.
  • Computer readable media includes both permanent and non-persistent, removable and non-removable media.
  • Information storage can be implemented by any method or technology. The information can be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
  • computer readable media does not include non-persistent computer readable media, such as modulated data signals and carrier waves.
  • Embodiments of the present application are described with reference to flowcharts and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG.
  • These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing terminal device to produce a machine such that instructions are executed by a processor of a computer or other programmable data processing terminal device
  • Means are provided for implementing the functions specified in one or more of the flow or in one or more blocks of the flow chart.
  • These computer program instructions can also be stored in a computer or other programmable data processing terminal device.
  • the computer readable memory that operates in a fixed manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device implemented in a block or a block and/or a block diagram of a flowchart or The functions specified in multiple boxes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Multimedia (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Stored Programmes (AREA)

Abstract

本申请实施例提供了一种表单标示符生成方法、表单分流方法和装置。其中，表单标示符生成方法，包括：生成唯一标示部分及路由标示部分，其中包括：根据预设的表单分流路由规则生成所述路由标示部分；依据所述唯一标示部分及所述路由标示部分组合生成所述表单的标示符。该生成表单唯一标示符的方法除了可以满足技术层面的全局ID唯一性外，还便于应用业务层在分库分表环境下的利用表单标示符中包含的路由信息进行表单分流操作，为分布式环境下大规模的海量数据的分库分表的拆分提供良好的扩展性和路由规则。

Description

表单标示符生成方法、表单分流方法和装置
本申请要求2015年07月22日递交的申请号为201510434905.4、发明名称为“表单标示符生成方法、表单分流方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及数据库技术领域，特别是涉及一种表单标示符生成方法、一种表单分流方法、一种表单标示符生成装置和一种表单分流装置。
背景技术
ID即标示符，可以在某个搜索域内唯一标示其中某个对象。在关系型数据库中，在单库单表环境下，一般会使用auto_increment属性或sequence对象作为生成ID的方法来唯一标示一条记录，这种方法在单库模式下能确保ID的唯一性。但是当系统规模扩大，单库单表不能满足业务数据的增长要求时，就要进行分库分表的扩容改造，每个分库分表的表单也需要生成一个全局唯一标示码ID。
目前，常用的分库分表环境下的表单ID生成方法有多种，例如：依据如当前计算机的MAC地址和时钟等参量使用多种算法来生成UUID，但是该方法生成的ID无任何业务层面的信息，如日期时间信息；还有根据时间戳、MAC地址、当前进程等信息组合生成的MongoDB Object ID，该生成方式虽然能够根据多部分信息组成一个唯一ID，但是其中包含的信息对应用业务层来说是透明的，应用业务层无法感知并利用这些信息。这些生成表单ID的方法给应用业务层在分库分表环境下的表单分流操作带来困难。
发明内容
本申请实施例所要解决的技术问题是提供一种表单标示符生成方法和一种表单分流方法，能够便于应用业务层的表单分流操作。
相应的，本申请实施例还提供了一种表单标示符生成装置和一种表单分流装置，用以保证上述方法的实现及应用。
为了解决上述问题，本申请公开了一种表单标示符生成方法，包括：
生成唯一标示部分及路由标示部分，其中包括：根据预设的表单分流路由规则生成所述路由标示部分；
依据所述唯一标示部分及所述路由标示部分组合生成所述表单的标示符。
进一步，所述根据预设的表单分流路由规则生成所述路由标示部分，包括：
根据预设的表单分库路由规则生成分库标示位。
进一步，所述根据预设的表单分流路由规则生成所述路由标示部分，还包括：
根据预设的表单分表路由规则生成分表标示位。
进一步，所述分库标示位及所述分表标示位均至少包括2位字符。
进一步，所述根据预设的表单分流路由规则生成所述路由标示部分，包括：
在用户标示符中选取特征位作为所述路由标示部分。
进一步，所述生成唯一标示部分，包括：
根据所述表单所对应的应用的关联参数生成第一标示部分，及根据所述表单的生成序列生成所述表单的序列号。
进一步，根据表单所对应的应用的关联参数生成所述第一标示部分，包括：
根据所述应用服务的日期生成日期标示位；
根据所述应用的启动参数生成数据版本位、系统版本位、系统标示位和业务标示位。
本申请实施例还公开了一种表单分流方法，包括：
接收网关分流的表单，其中，所述表单的标示符按照前述方法生成；
获取所述表单的标示符；
读取所述表单标示符中的路由标示部分；
根据所述表单的所述路由标示部分对所述表单进行分流。
进一步，所述根据所述表单的所述路由标示部分对所述表单进行分流，包括：
根据所述路由标示部分包含的分库标示位，将所述表单分流到与所述分库标示位对应的数据库中；
根据所述路由标示部分包含的分表标示位，将所述表单分流到所述数据库中与所述分表标示位对应的表集合中。
本申请实施例还公开了一种表单标示符生成装置，包括：
第一标示生成单元，被配置为生成唯一标示部分；
第二标示生成单元，被配置为根据预设的表单分流路由规则生成所述路由标示部分；
组合生成单元，被配置为依据所述唯一标示部分及所述路由标示部分组合生成所述表单的标示符。
进一步，所述第二标示生成单元，被配置为根据预设的表单分库路由规则生成分库 标示位。
进一步，所述第二标示生成单元，还被配置为根据预设的表单分表路由规则生成分表标示位。
本申请实施例还公开了一种表单分流装置，包括：
接收单元，被配置为接收网关分流的表单，其中，所述表单的标示符按照前述方法生成；
获取单元，被配置为获取所述表单的标示符；
读取单元，被配置为读取所述表单标示符中的路由标示部分；
分流单元，被配置为根据所述表单的所述路由标示部分对所述表单进行分流。
进一步，分流单元包括：
分库子单元，被配置为根据所述路由标示部分包含的分库标示位，将所述表单分流到与所述分库标示位对应的数据库中；
分表子单元，被配置为根据所述路由标示部分包含的分表标示位，将所述表单分流到所述数据库中与所述分表标示位对应的表集合中。
与现有技术相比，本申请实施例包括以下优点：
本申请实施例通过利用唯一标示部分及表单分流路由规则来生成表单的唯一标示符，使得应用业务层可以感知并利用这些信息进行表单分流，尤其可以利用标示符中的路由标示部分来依据预定的表单分流路由规则进行表单分流。该生成表单唯一标示符的方法除了可以满足技术层面的全局ID唯一性外，还便于应用业务层在分库分表环境下的利用表单标示符中包含的路由信息进行表单分流操作，为分布式环境下大规模的海量数据的分库分表的拆分提供良好的扩展性和路由规则。
附图说明
图1是本申请的一种表单标示符生成方法实施例的步骤流程图；
图2是本申请的一种生成第一标示部分的方法实施例的步骤流程图；
图3是本申请的一种生成路由标示部分的方法实施例的步骤流程图；
图4是本申请的一种表单标示符的结构示意图；
图5是本申请的一种表单分流方法实施例的步骤流程图；
图6是本申请的一种根据表单的路由标示部分对表单进行分流的方法实施例的步骤流程图；
图7是本申请的一种表单标示符装置实施例的结构框图；
图8是本申请的一种表单分流装置实施例的结构框图；
图9是本申请的一种分流单元实施例的结构框图。
具体实施方式
为使本申请的上述目的、特征和优点能够更加明显易懂，下面结合附图和具体实施方式对本申请作进一步详细的说明。
参照图1，示出了本申请的一种表单标示符生成方法实施例的步骤流程图，具体可以包括如下步骤：
步骤101，生成唯一标示部分及路由标示部分。
本实施例中，该生成表单唯一标示符的装置(以下简称该装置)首先生成组成该标示符的各部分，包括生成唯一标示部分及路由标示部分，其中唯一标示部分可以包括第一标示部分及序列号。具体可以是：根据表单所对应的应用的关联参数生成第一标示部分；根据预设的表单分流路由规则生成路由标示部分；根据表单的生成序列获得表单的序列号。各部分的生成可以依次或同时进行，次序不做限定。
其中，第一标示部分可以根据应用的启动参数等生成，具体可以包括日期信息、版本信息、业务信息等。
路由标示部分根据预先设定的表单分流时的路由规则来生成，例如表单分流路由规则为将同一用户的表单分流在同一数据库，则该生成的路由标示部分中需要包含用户的标识信息。在后续进行表单分流时，根据该路由标示部分进行分流即可实现预定的路由规则。
若表单的分流只是进行分库，则该路由标示部分可以只包含分库标示位，如果表单的分流是进行分库分表，则该路由标示部分可以包括分库标示位及分表标示位。
表单的序列号也即该表单生成的序号。为了支持足够的数据量，该序列号可以设置为8位。
步骤102，依据唯一标示部分及路由标示部分组合生成表单的标示符。
在获得上述第一标示部分、路由标示部分及序列号之后，本步骤可以按照一定的顺序或规则进行组合生成表单的唯一标示符，例如依次将第一标示部分、路由标示部分及序列号拼接在一起即可生成该表单的唯一标示符。
本申请实施例通过利用应用的关联参数、表单分流路由规则及表单的序列号来生成 表单的唯一标示符，使得应用业务层可以感知并利用这些信息进行表单分流，尤其可以利用标示符中的路由标示部分来依据预定的表单分流路由规则进行表单分流。该生成表单唯一标示符的方法除了可以满足技术层面的全局ID唯一性外，还便于应用业务层在分库分表环境下的利用表单标示符中包含的路由信息进行表单分流操作，为分布式环境下大规模的海量数据的分库分表的拆分提供良好的扩展性和路由规则。
在本申请的另一实施例中，该装置根据表单所对应的应用的关联参数生成第一标示部分的过程，如图2所示，可以包括：
步骤201，根据应用服务的日期生成日期标示位。
该装置可以获取当前应用服务的日期，并截取8位年月日字符串作为日期标示位。
步骤202，根据应用的启动参数生成数据版本位、系统版本位、系统标示位和业务标示位。
该装置可以根据应用的启动参数配置设置数据版本位和系统版本位，其中，数据版本位和系统版本位均可以是1位。
该装置可以根据应用启动参数设置3位的系统标示位，用于表示表单唯一标示符是由集群中的哪个应用生成的；
该装置根据应用启动参数设置3位业务标示位，用于表示表单标示符关联的这笔数据是什么业务。
上述步骤可以根据需要调整顺序，此处不做限定。
在本申请的另一实施例中，该装置根据预设的表单分流路由规则生成路由标示部分的过程，如图3所示，可以包括：
步骤301，根据预设的表单分库路由规则生成分库标示位。
该装置可以根据分库时需要遵循的路由规则生成该表单标示符中的分库标示位。例如，分库时需遵循的路由规则是相同用户的表单分流到同一数据库中，则可以从用户的标识信息中，例如uid(userId)中提取其中的特征位，如倒数第1、2位，作为表单标示符中的分库标示位。该分库标示位可以有两位，以支持100个物理库的扩展。
如果本实施例应用于分库分表的场景中，且分表也需要遵循某一路由规则，则还可以执行步骤302。
步骤302，根据预设的表单分表路由规则生成分表标示位。
该装置可以根据分表时需要遵循的路由规则生成该表单标示符中的分表标示位。例如，分表时需遵循的路由规则是相同用户的表单分流到同一数据库的同一表集合中，则 可以从用户的标识信息中，例如uid(userId)中提取其中的其它的特征位，如倒数第3、4位，作为表单标示符中的分表标示位。该分表标示位也可以有两位，以支持100个分表的扩展。
分库标示位和分表标示位的位数可以根据所需要的物理库和表集合数量来确定。
按照上述实施例的方法，在一具体实例中，假设根据应用服务的日期生成的日期标示位为20141212；根据应用的启动参数生成的数据版本位、系统版本位、系统标示位和业务标示位依次为0,1,001,001；在网上交易支付系统中，因为是基于用户登录所做的业务操作，因此该装置可根据uid(userId)来选取约定好的第几位作为这个分库、分表标示位，如用户的uid＝20188199965812，约定选取低位倒数第1,2位作为分库标示位，低位倒数第3,4位作为分表标示位；从类sequence获取nextValue作为表单标示符中的序列号，设定序列号为8位，位数不够前面填充0补齐，假设获取的序列号为28945699。
在获取上述信息后，即可拼接在一起生成如图4所示的由8位(日期)+1位(数据版本)+1位(系统版本位)+3位(系统标示位)+3位(业务标示位)+2位(分表标示位)+2位(分库标示位)+8位(序列号)，总共28位字符组成的表单的唯一标示符2014121201001001581228945699。
其中，表单标示符可根据前8位日期+序号按时间排序；单表可以支持足够的数据量，后8位序号一天可以最多1亿条数据记录；分库标示位可以支持100个物理库的扩展；分表标示位可以支持100个分表的扩展。
按照上述方法生成的表单标示符，每笔业务数据对应的表单都会明确的带有用户uid信息，因此同一个用户的表单都会在落到同一个分库分表中去，利于数据的聚集。通过该规范的业务全局唯一标示符，业务应用层就可以很容易做表单的分库分表且迁移成本小，为整个的业务的数据架构层带来非常良好的基础，业务数据的落地具备也可以有很好的扩展性。
参照图5，示出了本申请的一种表单分流方法实施例的步骤流程图，具体可以包括如下步骤：
步骤501，接收网关分流的表单。
本实施例中，该表单分流装置具体可以是应用服务器等。其中，该表单的标示符可以按照前述实施例的方法来生成。该表单标示符中包括根据表单所对应的应用的关联参数生成的第一标示部分；根据预设的表单分流路由规则生成的路由标示部分；根据表单的生成序列获得的表单的序列号。
步骤502，获取表单的标示符。
步骤503，读取表单标示符中的路由标示部分。
该表单标示符中的路由标示部分中包含有表单的分流路由规则。
步骤504，根据表单的路由标示部分对表单进行分流。
该表单分流装置可以根据路由标示部分包含的信息进行表单分流，据此获得的分流结果即可体现预定的分流路由规则。
本申请实施例在分库分表的环境下，通过利用表单标示符中包含的路由信息可以很容易地进行表单的分库分表且迁移成本小，为整个的业务的数据架构层带来非常良好的基础，业务数据的落地具备也可以有很好的扩展性。
在另一实施例中，该表单分流装置根据表单的路由标示部分对表单进行分流的过程，如图6所示，可以包括：
步骤601，根据路由标示部分包含的分库标示位，将表单分流到与分库标示位对应的数据库中。
本实施例中的表单标示符中路由标示部分包含分库标示位和分表标示位，例如，表单标示符为2014121201001001581228945699，分库标示位为12，分表标示位为58，本步骤将该表单分流到数据库12中。
步骤602，根据路由标示部分包含的分表标示位，将表单分流到数据库中与分表标示位对应的表集合中。
本步骤继续将上述表单分流到数据库12中与分表标示位58对应的表集合中。
需要说明的是，对于方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本申请实施例并不受所描述的动作顺序的限制，因为依据本申请实施例，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作并不一定是本申请实施例所必须的。
参照图7，示出了本申请一种表单标示符装置实施例的结构框图，具体可以包括如下单元：
第一标示生成单元701，被配置为生成唯一标示部分。
第二标示生成单元702，被配置为根据预设的表单分流路由规则生成所述路由标示部分。
组合生成单元703，被配置为依据所述唯一标示部分及所述路由标示部分组合生成所述表单的标示符。
该装置通过利用应用的关联参数、表单分流路由规则及表单的序列号来生成表单的唯一标示符，使得应用业务层可以感知并利用这些信息进行表单分流，尤其可以利用标示符中的路由标示部分来依据预定的表单分流路由规则进行表单分流。该生成表单唯一标示符的装置除了可以满足技术层面的全局ID唯一性外，还便于应用业务层在分库分表环境下的利用表单标示符中包含的路由信息进行表单分流操作，为分布式环境下大规模的海量数据的分库分表的拆分提供良好的扩展性和路由规则。
在另一实施例中，第二标示生成单元702，可以被配置为根据预设的表单分库路由规则生成分库标示位；还可以被配置为根据预设的表单分表路由规则生成分表标示位。
第二标示生成单元702，具体可以被配置为在用户标示符中选取特征位作为所述路由标示部分。
其中，分库标示位及所述分表标示位均至少包括2位字符，所述序列号至少包括8位字符。
另一实施例中，第一标示生成单元701可以被配置为根据所述表单所对应的应用的关联参数生成第一标示部分，及根据所述表单的生成序列生成所述表单的序列号。可以进一步包括：
第一生成子单元，被配置为根据所述应用服务的日期生成日期标示位。
第二生成子单元，被配置为根据所述应用的启动参数生成数据版本位、系统版本位、系统标示位和业务标示位。
第三生成子单元，被配置为根据所述表单的生成序列生成所述表单的序列号。
其中，第一生成子单元和第二生成子单元生成的日期标示位、数据版本位、系统版本位、系统标示位和业务标示位作为前述第一标示部分。第三生成子单元生成表单的序列号。
参照图8，示出了本申请一种表单分流装置实施例的结构框图，具体可以包括如下单元：
接收单元801，被配置为接收网关分流的表单。
获取单元802，被配置为获取所述表单的标示符。
读取单元803，被配置为读取所述表单标示符中的路由标示部分。
分流单元804，被配置为根据所述表单的所述路由标示部分对所述表单进行分流。
该装置在分库分表的环境下，通过利用表单标示符中包含的路由信息可以很容易地进行表单的分库分表且迁移成本小，为整个的业务的数据架构层带来非常良好的基础，业务数据的落地具备也可以有很好的扩展性。
在另一实施例中，如图9所示，分流单元804可以进一步包括：
分库子单元901，被配置为根据所述路由标示部分包含的分库标示位，将所述表单分流到与所述分库标示位对应的数据库中。
分表子单元902，被配置为根据所述路由标示部分包含的分表标示位，将所述表单分流到所述数据库中与所述分表标示位对应的表集合中。
本申请实施例还提供了一种服务器，包括存储器和处理器。
处理器与存储器通过总线相互连接；总线可以是ISA总线、PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。
其中，存储器用于存储一段程序，具体地，程序可以包括程序代码，所述程序代码包括计算机操作指令。存储器可能包含高速RAM存储器，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。
处理器用于读取存储器中的程序代码，执行以下步骤：
生成唯一标示部分及路由标示部分，其中包括：根据预设的表单分流路由规则生成所述路由标示部分；
依据所述唯一标示部分及所述路由标示部分组合生成所述表单的标示符。
本申请实施例还提供了一种服务器，包括存储器、收发器和处理器。
处理器与存储器、收发器通过总线相互连接；总线可以是ISA总线、PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。
其中，存储器用于存储一段程序，具体地，程序可以包括程序代码，所述程序代码包括计算机操作指令。存储器可能包含高速RAM存储器，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。
收发器用于接收网关分流的表单。
处理器用于读取存储器中的程序代码，执行以下步骤：
获取所述表单的标示符；
读取所述表单标示符中的路由标示部分；
根据所述表单的所述路由标示部分对所述表单进行分流。
对于装置实施例而言，由于其与方法实施例基本相似，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
本说明书中的各个实施例均采用递进的方式描述，每个实施例重点说明的都是与其他实施例的不同之处，各个实施例之间相同相似的部分互相参见即可。
本领域内的技术人员应明白，本申请实施例的实施例可提供为方法、装置、或计算机程序产品。因此，本申请实施例可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
在一个典型的配置中，所述计算机设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括非持续性的电脑可读媒体(transitory media)，如调制的数据信号和载波。
本申请实施例是参照根据本申请实施例的方法、终端设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理终端设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理终端设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理终端设备以特 定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理终端设备上，使得在计算机或其他可编程终端设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程终端设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请实施例的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例做出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请实施例范围的所有变更和修改。
最后，还需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者终端设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者终端设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者终端设备中还存在另外的相同要素。
以上对本申请所提供的一种表单标示符生成方法、一种表单分流方法、一种表单标示符生成装置和一种表单分流装置，进行了详细介绍，本文中应用了具体个例对本申请的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本申请的方法及其核心思想；同时，对于本领域的一般技术人员，依据本申请的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本申请的限制。

Claims (14)

  1. 一种表单标示符生成方法，其特征在于，包括：
    生成唯一标示部分及路由标示部分，其中包括：根据预设的表单分流路由规则生成所述路由标示部分；
    依据所述唯一标示部分及所述路由标示部分组合生成所述表单的标示符。
  2. 根据权利要求1所述的方法，其特征在于，所述根据预设的表单分流路由规则生成所述路由标示部分，包括：
    根据预设的表单分库路由规则生成分库标示位。
  3. 根据权利要求2所述的方法，其特征在于，所述根据预设的表单分流路由规则生成所述路由标示部分，还包括：
    根据预设的表单分表路由规则生成分表标示位。
  4. 根据权利要求3所述的方法，其特征在于，所述分库标示位及所述分表标示位均至少包括2位字符。
  5. 根据权利要求1所述的方法，其特征在于，所述根据预设的表单分流路由规则生成所述路由标示部分，包括：
    在用户标示符中选取特征位作为所述路由标示部分。
  6. 根据权利要求1至5中任意一项所述的方法，其特征在于，所述生成唯一标示部分，包括：
    根据所述表单所对应的应用的关联参数生成第一标示部分，及根据所述表单的生成序列生成所述表单的序列号。
  7. 根据权利要求6所述的方法，其特征在于，所述根据表单所对应的应用的关联参数生成所述第一标示部分，包括：
    根据所述应用服务的日期生成日期标示位；
    根据所述应用的启动参数生成数据版本位、系统版本位、系统标示位和业务标示位。
  8. 一种表单分流方法，其特征在于，包括：
    接收网关分流的表单，其中，所述表单的标示符按照权利要求1至7中任意一项所述的方法生成；
    获取所述表单的标示符；
    读取所述表单标示符中的路由标示部分；
    根据所述表单的所述路由标示部分对所述表单进行分流。
  9. 根据权利要求8所述的方法，其特征在于，所述根据所述表单的所述路由标示部分对所述表单进行分流，包括：
    根据所述路由标示部分包含的分库标示位，将所述表单分流到与所述分库标示位对应的数据库中；
    根据所述路由标示部分包含的分表标示位，将所述表单分流到所述数据库中与所述分表标示位对应的表集合中。
  10. 一种表单标示符生成装置，其特征在于，包括：
    第一标示生成单元，被配置为生成唯一标示部分；
    第二标示生成单元，被配置为根据预设的表单分流路由规则生成所述路由标示部分；
    组合生成单元，被配置为依据所述唯一标示部分及所述路由标示部分组合生成所述表单的标示符。
  11. 根据权利要求10所述的装置，其特征在于，
    所述第二标示生成单元，被配置为根据预设的表单分库路由规则生成分库标示位。
  12. 根据权利要求11所述的装置，其特征在于，
    所述第二标示生成单元，还被配置为根据预设的表单分表路由规则生成分表标示位。
  13. 一种表单分流装置，其特征在于，包括：
    接收单元，被配置为接收网关分流的表单，其中，所述表单的标示符按照权利要求1至7中任意一项所述的方法生成；
    获取单元，被配置为获取所述表单的标示符；
    读取单元，被配置为读取所述表单标示符中的路由标示部分；
    分流单元，被配置为根据所述表单的所述路由标示部分对所述表单进行分流。
  14. 根据权利要求13所述的装置，其特征在于，分流单元包括：
    分库子单元，被配置为根据所述路由标示部分包含的分库标示位，将所述表单分流到与所述分库标示位对应的数据库中；
    分表子单元，被配置为根据所述路由标示部分包含的分表标示位，将所述表单分流到所述数据库中与所述分表标示位对应的表集合中。
PCT/CN2016/089867 2015-07-22 2016-07-13 表单标示符生成方法、表单分流方法和装置 WO2017012492A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510434905.4 2015-07-22
CN201510434905.4A CN106372081B (zh) 2015-07-22 2015-07-22 表单标示符生成方法、表单分流方法和装置

Publications (1)

Publication Number Publication Date
WO2017012492A1 true WO2017012492A1 (zh) 2017-01-26

Family

ID=57833713

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/089867 WO2017012492A1 (zh) 2015-07-22 2016-07-13 表单标示符生成方法、表单分流方法和装置

Country Status (2)

Country Link
CN (1) CN106372081B (zh)
WO (1) WO2017012492A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110955664A (zh) * 2019-12-03 2020-04-03 中国建设银行股份有限公司 分库分表消息路由方法及装置
CN111897791A (zh) * 2020-07-15 2020-11-06 银联商务股份有限公司 一种业务分流方法、装置、设备和存储介质
CN113849458A (zh) * 2021-09-18 2021-12-28 四川长虹网络科技有限责任公司 MongoDB中间件及数据存储方法和数据迁移方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030110150A1 (en) * 2001-11-30 2003-06-12 O'neil Patrick Eugene System and method for relational representation of hierarchical data
US20070208753A1 (en) * 2004-12-30 2007-09-06 Ncr Corporation Routing database requests among multiple active database systems
CN102467521A (zh) * 2010-11-08 2012-05-23 北大方正集团有限公司 一种易扩展的多级分类检索方法及系统
US20140129592A1 (en) * 2012-11-06 2014-05-08 Business Objects Software Ltd. Build pooled data source based on hana saml login

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102402730A (zh) * 2010-09-15 2012-04-04 金蝶软件（中国）有限公司 一种动态业务数据分流方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030110150A1 (en) * 2001-11-30 2003-06-12 O'neil Patrick Eugene System and method for relational representation of hierarchical data
US20070208753A1 (en) * 2004-12-30 2007-09-06 Ncr Corporation Routing database requests among multiple active database systems
CN102467521A (zh) * 2010-11-08 2012-05-23 北大方正集团有限公司 一种易扩展的多级分类检索方法及系统
US20140129592A1 (en) * 2012-11-06 2014-05-08 Business Objects Software Ltd. Build pooled data source based on hana saml login

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110955664A (zh) * 2019-12-03 2020-04-03 中国建设银行股份有限公司 分库分表消息路由方法及装置
CN111897791A (zh) * 2020-07-15 2020-11-06 银联商务股份有限公司 一种业务分流方法、装置、设备和存储介质
CN111897791B (zh) * 2020-07-15 2024-01-12 银联商务股份有限公司 一种业务分流方法、装置、设备和存储介质
CN113849458A (zh) * 2021-09-18 2021-12-28 四川长虹网络科技有限责任公司 MongoDB中间件及数据存储方法和数据迁移方法

Also Published As

Publication number Publication date
CN106372081A (zh) 2017-02-01
CN106372081B (zh) 2019-09-17

Similar Documents

Publication Publication Date Title
WO2020023733A1 (en) Blockchain-based cross-chain data access method and apparatus
WO2017053892A1 (en) Method and apparatus for transferring data between databases
US10223435B2 (en) Data transfer between multiple databases
CN106897342B (zh) 一种数据校验方法和设备
CN104079614B (zh) 用于分布式发布订阅系统消息有序获取的方法和系统
CN108399175B (zh) 一种数据存储、查询方法及其装置
WO2013097546A1 (en) Assisting query and querying
US20140046899A1 (en) Method and Apparatus of Implementing Navigation of Product Properties
WO2017012492A1 (zh) 表单标示符生成方法、表单分流方法和装置
US9098508B2 (en) Aggregating identifiers for media items
WO2018107991A1 (zh) 一种实体信息验证方法及装置
WO2017097159A1 (zh) 一种随机字符串生成方法及装置
TW201702870A (zh) 一種資源分配方法和裝置
CN110334094A (zh) 一种基于倒排索引的数据查询方法、系统、装置及设备
CN111343241A (zh) 一种图数据更新方法、装置及系统
CN114610951A (zh) 数据处理方法、装置、电子设备及可读存储介质
CN109446298A (zh) 模板匹配方法及装置、计算机设备及可读介质
CN106570029B (zh) 分布式关系型数据库的数据处理方法及系统
CN110928895B (zh) 一种数据查询、数据表建立方法、装置及设备
TWI690809B (zh) 表單分流方法和裝置
CN108228604B (zh) 基于内存对象的模型构建方法、信息查询方法及装置
TW202011323A (zh) 網際網路交易定位方法、裝置及伺服器
CN106886546B (zh) 一种数据网站的构建方法和设备
TW201734838A (zh) 樣本序列化方法和裝置
CN107870908B (zh) 一种信息获取方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16827183

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16827183

Country of ref document: EP

Kind code of ref document: A1