CN115168324A - Database configuration and access method in SAAS platform - Google Patents
Database configuration and access method in SAAS platformDownload PDFInfo
- Publication number
- CN115168324A CN115168324ACN202210832098.1ACN202210832098ACN115168324ACN 115168324 ACN115168324 ACN 115168324ACN 202210832098 ACN202210832098 ACN 202210832098ACN 115168324 ACN115168324 ACN 115168324A
- Authority
- CN
- China
- Prior art keywords
- database
- configuration
- platform
- information
- library
- 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
Images
Classifications
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24552—Database cache management
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F16/278—Data partitioning, e.g. horizontal or vertical partitioning
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/80—Database-specific techniques
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- Computing Systems (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Translated fromChinese
Description
Translated fromChinese技术领域technical field
本发明涉及数据库配置领域，特别是一种SAAS平台中数据库配置及访问方法。The invention relates to the field of database configuration, in particular to a database configuration and access method in a SAAS platform.
背景技术Background technique
SAAS平台数据库中存储海量数据，在日常访问和存储数据时，访问速度慢查询效率低下，单个数据库服务器，用户量在一直增长的过程中对数据库服务器造成的压力过大，存在宕机的可能性，同时因为用户量时刻在增长数据也一直增长，数据存储量可能会达到单个数据库存储的极限。A large amount of data is stored in the SAAS platform database. When accessing and storing data on a daily basis, the access speed is slow and the query efficiency is low. For a single database server, the continuous increase in the number of users puts too much pressure on the database server, and there is a possibility of downtime. , At the same time, because the number of users is constantly growing, the data is also growing, and the data storage volume may reach the limit of a single database storage.
因为数据库存储的数据量大，平台在访问的过程中，对数据库进行的读写操作效率低下，同时因为saas平台使用用户量大并发量高，对服务器的硬件要求也比较严格。Due to the large amount of data stored in the database, the read and write operations on the database are inefficient during the access process of the platform. At the same time, because the saas platform uses a large number of users and high concurrency, the hardware requirements for the server are also relatively strict.
发明内容SUMMARY OF THE INVENTION
本发明的目的在于提供一种SAAS平台中数据库配置及访问方法，解决现有SAAS平台中数据库因为用户量的持续增加，数据库服务器压力过大的问题。The purpose of the present invention is to provide a database configuration and access method in the SAAS platform, so as to solve the problem of excessive pressure on the database server due to the continuous increase of the number of users of the database in the existing SAAS platform.
为解决上述的技术问题，本发明采用以下技术方案：In order to solve the above-mentioned technical problems, the present invention adopts the following technical solutions:
一种SAAS平台中数据库配置及访问方法，包括如下步骤：a、先将平台数据库根据业务进行拆分主要拆分为：配置中心库、配置库和业务库；b、拆分完成后用户根据域名访问平台，访问平台时，平台根据域名在缓存中查找用户需要访问的对应库，如缓存中没有记录则到配置中心库中进行查找，查找后把结果存放到缓存中，同时访问配置对应的数据库。A method for configuring and accessing a database in a SAAS platform, comprising the following steps: a. firstly, the platform database is divided into: a configuration center library, a configuration library and a business library according to the business; When accessing the platform, when accessing the platform, the platform searches the cache for the corresponding library that the user needs to access according to the domain name. If there is no record in the cache, it will search in the configuration center library. After searching, the result will be stored in the cache, and the database corresponding to the configuration will be accessed at the same time. .
在平台中配置中心库只有一个，根据不同的租户会配置不同的配置库和不同的业务库，会跟进租户内预估使用用户量来进行评估配置，如50万以上用户量的租户使用单独一个业务库十个50万以上用户量的租户使用一个配置，在saas平台通过配置进行分库操作，可以解决数据库服务器的I/O能力限制，增加可扩展性。There is only one configuration central library in the platform. Different configuration libraries and different business libraries will be configured according to different tenants, and the estimated user volume in the tenant will be followed for evaluation and configuration. For example, tenants with more than 500,000 users use separate Ten tenants with more than 500,000 users in a business database use one configuration, and the sub-database operation is performed on the saas platform through configuration, which can solve the I/O capability limitation of the database server and increase the scalability.
作为本发明的进一步优选，所述步骤a中的配置中心库关联有主数据库和从数据库，所述主数据库和从数据库采用读写分离配置，平台中对数据库操作的脚本配置在数据配置中心库中的sql脚本表中，平台会跟进配置的操作脚本名称到缓存中查找具体才操作语句，如缓存中没有找到会到配置中心库中的sql脚本表中进行查询，并保存在缓存中并对数据库进行访问，操作的脚本类型为默认default则脚本读操作访问从数据库，写操作访问主数据库，操作的脚本类型为主master则访问主数据库，操作的脚本类型为从slave则访问从数据库。As a further preference of the present invention, the configuration center library in the step a is associated with a master database and a slave database, the master database and the slave database are configured with read-write separation, and the scripts for database operations in the platform are configured in the data configuration center library In the sql script table in the configuration center, the platform will follow up the configured operation script name to the cache to find the specific operation statement. To access the database, the script type of the operation is the default default, the script read operation accesses the slave database, the write operation accesses the master database, the script type of the operation is the master master, and the script type of the operation is the slave database. Access the slave database.
采用读写分离配置，这样当主数据库发生宕机了时可启用从数据库，用于故障切换，有效解决数据库宕机对平台造成的影响，可以使用“热备份”，可以有效解决数据丢失的问题，避免影响平台业务和用户使用，可以采用读写分离主服务器可以只用于写操作，从服务器只用于读取，用于查询服务，读写分离可以减少数据库压力，提高性能，同时为解决主从同步引起的数据延迟问题，通过配置在数据时效性要求没有那么高的场景下采用读取从库数据，在写了之后立马就要保证可以查到的业务场景，采用强制读主库的方式，这样就可以保证读到数据，针对时效不高的数据通过读写分离缓解数据库压力，最大限度的提高saas平台中读取数据的速度和并发量。The read-write separation configuration is adopted, so that when the primary database is down, the secondary database can be enabled for failover, which can effectively solve the impact of database downtime on the platform. "Hot backup" can be used to effectively solve the problem of data loss. To avoid affecting the platform business and user use, you can use read-write separation. The master server can only be used for write operations, and the slave server is only used for reading and query services. Read-write separation can reduce database pressure and improve performance. For the data delay problem caused by slave synchronization, through configuration, in the scenario where the data timeliness requirement is not so high, the slave database data is read, and the business scenario that can be found must be guaranteed immediately after writing, and the method of forcing the master database to be read is adopted. , so that the data can be read, and the database pressure can be relieved through read-write separation for data with low timeliness, and the speed and concurrency of data read in the saas platform can be maximized.
作为本发明的进一步优选，如管理员改变sql脚本配置内容，在改变后会清空缓存信息。As a further preference of the present invention, if the administrator changes the configuration content of the sql script, the cached information will be cleared after the change.
作为本发明的进一步优选，所述步骤a中的配置中心库主要存储分库配置信息、kv配置信息、服务配置信息、sql脚本及sql脚本访问配置信息。As a further preference of the present invention, the configuration center library in the step a mainly stores sub-database configuration information, kv configuration information, service configuration information, sql script and sql script access configuration information.
作为本发明的进一步优选，所述步骤a中的配置库主要存储租户初始化脚本、元数据、租户自定义元数据信息、菜单、租户自定义菜单、常量、用户基本信息及相关授权。As a further preference of the present invention, the configuration repository in the step a mainly stores tenant initialization scripts, metadata, tenant custom metadata information, menus, tenant custom menus, constants, basic user information and related authorizations.
作为本发明的进一步优选，所述步骤a中的业务库主要存储平台基础设置、学生信息、教师信息、学生学习产生的相关数据、学生考试流程相关数据、学生毕业流程相关数据。As a further preference of the present invention, the business database in step a mainly stores platform basic settings, student information, teacher information, related data generated by student learning, student exam process related data, and student graduation process related data.
作为本发明的进一步优选，所述步骤b中如管理员改变配置中心中配置信息，在改变后会清空缓存信息，方便用户再次进入时使用的是最新配置信息。As a further preference of the present invention, in the step b, if the administrator changes the configuration information in the configuration center, the cached information will be cleared after the change, so that the latest configuration information is used when the user enters again.
与现有技术相比，本发明至少能达到以下有益效果中的一项：Compared with the prior art, the present invention can achieve at least one of the following beneficial effects:
1、在平台中配置中心库只有一个，根据不同的租户会配置不同的配置库和不同的业务库，会跟进租户内预估使用用户量来进行评估配置，如50万以上用户量的租户使用单独一个业务库十个50万以上用户量的租户使用一个配置，在saas平台通过配置进行分库操作，可以解决数据库服务器的I/O能力限制，增加可扩展性。。1. There is only one configuration central library in the platform. According to different tenants, different configuration libraries and different business libraries will be configured, and the estimated number of users in the tenant will be followed for evaluation and configuration, such as tenants with more than 500,000 users. Ten tenants with more than 500,000 users using a single business database use one configuration, and perform database sub-database operations through configuration on the saas platform, which can solve the I/O capability limitation of the database server and increase scalability. .
2、采用读写分离配置，这样当主数据库发生宕机了时可启用从数据库，用于故障切换，有效解决数据库宕机对平台造成的影响，可以使用“热备份”，可以有效解决数据丢失的问题，避免影响平台业务和用户使用，可以采用读写分离主服务器可以只用于写操作，从服务器只用于读取，用于查询服务，读写分离可以减少数据库压力，提高性能，同时为解决主从同步引起的数据延迟问题，通过配置在数据时效性要求没有那么高的场景下采用读取从库数据，在写了之后立马就要保证可以查到的业务场景，采用强制读主库的方式，这样就可以保证读到数据，针对时效不高的数据通过读写分离缓解数据库压力，最大限度的提高saas平台中读取数据的速度和并发量。2. The read-write separation configuration is adopted, so that when the primary database is down, the secondary database can be enabled for failover to effectively solve the impact of database downtime on the platform. "Hot backup" can be used to effectively solve the problem of data loss. To avoid affecting platform business and user use, you can use read-write separation. The master server can only be used for write operations, and the slave server is only used for reading and query services. Read-write separation can reduce database pressure and improve performance. To solve the problem of data delay caused by master-slave synchronization, read slave database data through configuration in scenarios where data timeliness requirements are not so high. After writing, it is necessary to ensure the business scenarios that can be found, and use forced reading of master database. In this way, the data can be guaranteed to be read, and the database pressure can be relieved through read-write separation for data with low timeliness, and the speed and concurrency of data read in the saas platform can be maximized.
附图说明Description of drawings
图1 为本发明SAAS平台中数据库分库示意图。FIG. 1 is a schematic diagram of database sub-database in the SAAS platform of the present invention.
图2为本发明数据库主从读写配置示意图。FIG. 2 is a schematic diagram of a master-slave read-write configuration of a database according to the present invention.
具体实施方式Detailed ways
为使本发明实施方式的目的、技术方案和优点更加清楚，下面将结合本发明实施方式中的附图，对本发明实施方式中的技术方案进行清楚、完整地描述，显然，所描述的实施方式是本发明一部分实施方式，而不是全部的实施方式。通常在此处附图中描述和示出的本发明实施方式的组件可以以各种不同的配置来布置和设计。In order to make the purposes, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments These are some embodiments of the present invention, but not all of them. The components of the embodiments of the invention generally described and illustrated in the drawings herein may be arranged and designed in a variety of different configurations.
因此，以下对在附图中提供的本发明的实施方式的详细描述并非旨在限制要求保护的本发明的范围，而是仅仅表示本发明的选定实施方式。基于本发明中的实施方式，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施方式，都属于本发明保护的范围。Accordingly, the following detailed description of the embodiments of the invention provided in the accompanying drawings is not intended to limit the scope of the invention as claimed, but is merely representative of selected embodiments of the invention. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.
需要说明的是，在不冲突的情况下，本发明中的实施方式及实施方式中的特征可以相互组合。It should be noted that the embodiments of the present invention and the features of the embodiments may be combined with each other without conflict.
应注意到：相似的标号和字母在下面的附图中表示类似项，因此，一旦某一项在一个附图中被定义，则在随后的附图中不需要对其进行进一步定义和解释。It should be noted that like numerals and letters refer to like items in the following figures, so once an item is defined in one figure, it does not require further definition and explanation in subsequent figures.
在本发明的描述中，需要说明的是，术语“中心”、“上”、“下”、“左”、“右”、“竖直”、“水平”、“内”、“外”等指示的方位或位置关系为基于附图所示的方位或位置关系，或者是该发明产品使用时惯常摆放的方位或位置关系，或者是本领域技术人员惯常理解的方位或位置关系，仅是为了便于描述本发明和简化描述，而不是指示或暗示所指的装置或元件必须具有特定的方位、以特定的方位构造和操作，因此不能理解为对本发明的限制。此外，术语“第一”、“第二”等仅用于区分描述，而不能理解为指示或暗示相对重要性。In the description of the present invention, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc. The indicated orientation or positional relationship is based on the orientation or positional relationship shown in the accompanying drawings, or the orientation or positional relationship that is usually placed when the product of the invention is used, or the orientation or positional relationship that is commonly understood by those skilled in the art. In order to facilitate the description of the present invention and simplify the description, it is not indicated or implied that the indicated device or element must have a particular orientation, be constructed and operated in a particular orientation, and therefore should not be construed as limiting the present invention. Furthermore, the terms "first", "second", etc. are only used to differentiate the description and should not be construed to indicate or imply relative importance.
在本发明的描述中，还需要说明的是，除非另有明确的规定和限定，术语“设置”、“安装”、“相连”、“连接”应做广义理解，例如，可以是固定连接，也可以是可拆卸连接，或一体地连接；可以是机械连接，也可以是电连接；可以是直接相连，也可以通过中间媒介间接相连，可以是两个元件内部的连通。对于本领域的普通技术人员而言，可以具体情况理解上述术语在本发明中的具体含义。In the description of the present invention, it should also be noted that, unless otherwise expressly specified and limited, the terms "arranged", "installed", "connected" and "connected" should be understood in a broad sense, for example, it may be a fixed connection, It can also be a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or an indirect connection through an intermediate medium, or the internal communication between the two components. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood in specific situations.
具体实施例1：Specific embodiment 1:
一种SAAS平台中数据库配置及访问方法，包括如下步骤：a、先将平台数据库根据业务进行拆分主要拆分为：配置中心库、配置库和业务库；b、拆分完成后用户根据域名访问平台，访问平台时，平台根据域名在缓存中查找用户需要访问的对应库，如缓存中没有记录则到配置中心库中进行查找，查找后把结果存放到缓存中，同时访问配置对应的数据库。A method for configuring and accessing a database in a SAAS platform, comprising the following steps: a. firstly, the platform database is divided into: a configuration center library, a configuration library and a business library according to the business; When accessing the platform, when accessing the platform, the platform searches the cache for the corresponding library that the user needs to access according to the domain name. If there is no record in the cache, it will search in the configuration center library. After searching, the result will be stored in the cache, and the database corresponding to the configuration will be accessed at the same time. .
在平台中配置中心库只有一个，根据不同的租户会配置不同的配置库和不同的业务库，会跟进租户内预估使用用户量来进行评估配置，如50万以上用户量的租户使用单独一个业务库十个50万以上用户量的租户使用一个配置，在saas平台通过配置进行分库操作，可以解决数据库服务器的I/O能力限制，增加可扩展性。There is only one configuration central library in the platform. Different configuration libraries and different business libraries will be configured according to different tenants, and the estimated user volume in the tenant will be followed for evaluation and configuration. For example, tenants with more than 500,000 users use separate Ten tenants with more than 500,000 users in a business database use one configuration, and the sub-database operation is performed on the saas platform through configuration, which can solve the I/O capability limitation of the database server and increase the scalability.
具体实施例2：Specific embodiment 2:
本实施例是在具体实施例1的基础上对步骤a进行了进一步的说明，所述步骤a中的配置中心库关联有主数据库和从数据库，所述主数据库和从数据库采用读写分离配置，平台中对数据库操作的脚本配置在数据配置中心库中的sql脚本表中，平台会跟进配置的操作脚本名称到缓存中查找具体才操作语句，如缓存中没有找到会到配置中心库中的sql脚本表中进行查询，并保存在缓存中并对数据库进行访问，操作的脚本类型为默认default则脚本读操作访问从数据库，写操作访问主数据库，操作的脚本类型为主master则访问主数据库，操作的脚本类型为从slave则访问从数据库。This embodiment further describes step a on the basis of specific embodiment 1. The configuration center database in step a is associated with a master database and a slave database, and the master database and slave database are configured with read-write separation. , the script of the database operation in the platform is configured in the sql script table in the data configuration center library, the platform will follow the configured operation script name to the cache to find the specific operation statement, if it is not found in the cache, it will go to the configuration center library Query in the sql script table, save it in the cache and access the database. The script type of the operation is the default default, the script read operation accesses the slave database, the write operation accesses the master database, and the script type of the operation is the master master, which accesses the master database. Database, the script type of the operation is from the slave to access the slave database.
采用读写分离配置，这样当主数据库发生宕机了时可启用从数据库，用于故障切换，有效解决数据库宕机对平台造成的影响，可以使用“热备份”，可以有效解决数据丢失的问题，避免影响平台业务和用户使用，可以采用读写分离主服务器可以只用于写操作，从服务器只用于读取，用于查询服务，读写分离可以减少数据库压力，提高性能，同时为解决主从同步引起的数据延迟问题，通过配置在数据时效性要求没有那么高的场景下采用读取从库数据，在写了之后立马就要保证可以查到的业务场景，采用强制读主库的方式，这样就可以保证读到数据，针对时效不高的数据通过读写分离缓解数据库压力，最大限度的提高saas平台中读取数据的速度和并发量The read-write separation configuration is adopted, so that when the primary database is down, the secondary database can be enabled for failover, which can effectively solve the impact of database downtime on the platform. "Hot backup" can be used to effectively solve the problem of data loss. To avoid affecting the platform business and user use, you can use read-write separation. The master server can only be used for write operations, and the slave server is only used for reading and query services. Read-write separation can reduce database pressure and improve performance. For the data delay problem caused by slave synchronization, through configuration, in the scenario where the data timeliness requirement is not so high, the slave database data is read, and the business scenario that can be found must be guaranteed immediately after writing, and the method of forcing the master database to be read is adopted. , so that the data can be read, and the database pressure can be relieved through read-write separation for data with low timeliness, and the speed and concurrency of data read in the saas platform can be maximized.
具体实施例3：Specific embodiment 3:
本实施例是在具体实施例2的基础上对管理员改变sql脚本配置内容进行了进一步的说明，如管理员改变sql脚本配置内容，在改变后会清空缓存信息。This embodiment further describes how the administrator changes the configuration content of the sql script on the basis of the specific embodiment 2. For example, if the administrator changes the configuration content of the sql script, the cached information will be cleared after the change.
具体实施例4：Specific embodiment 4:
本实施例是在具体实施例1的基础上对步骤a进行了进一步的说明，所述步骤a中的配置中心库主要存储分库配置信息、kv配置信息、服务配置信息、sql脚本及sql脚本访问配置信息。This embodiment further describes step a on the basis of specific embodiment 1. The configuration center library in step a mainly stores sub-database configuration information, kv configuration information, service configuration information, sql script and sql script Access configuration information.
具体实施例5：Specific embodiment 5:
本实施例是在具体实施例1的基础上对步骤a进行了进一步的说明，所述步骤a中的配置库主要存储租户初始化脚本、元数据、租户自定义元数据信息、菜单、租户自定义菜单、常量、用户基本信息及相关授权。This embodiment further describes step a on the basis of specific embodiment 1. The configuration repository in step a mainly stores tenant initialization scripts, metadata, tenant-defined metadata information, menus, and tenant-defined metadata. Menus, constants, basic user information and related authorizations.
具体实施例6：Specific embodiment 6:
本实施例是在具体实施例1的基础上对步骤a进行了进一步的说明，所述步骤a中的业务库主要存储平台基础设置、学生信息、教师信息、学生学习产生的相关数据、学生考试流程相关数据、学生毕业流程相关数据。This embodiment further describes step a on the basis of specific embodiment 1. The business database in step a mainly stores platform basic settings, student information, teacher information, relevant data generated by student learning, and student exams. Process-related data, student graduation process-related data.
具体实施例7：Specific embodiment 7:
本实施例是在具体实施例1的基础上对步骤b进行了进一步的说明，所述步骤b中如管理员改变配置中心中配置信息，在改变后会清空缓存信息，方便用户再次进入时使用的是最新配置信息。This embodiment further describes step b on the basis of specific embodiment 1. In step b, if the administrator changes the configuration information in the configuration center, the cached information will be cleared after the change, which is convenient for the user to use when entering again. is the latest configuration information.
尽管参照前述实施例对本发明进行了详细的说明，对于本领域的技术人员来说，其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换,凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。Although the present invention has been described in detail with reference to the foregoing embodiments, for those skilled in the art, it is still possible to modify the technical solutions described in the foregoing embodiments, or to perform equivalent replacements for some of the technical features. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.
Claims (7)
Translated fromChinesePriority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210832098.1ACN115168324A (en) | 2022-07-15 | 2022-07-15 | Database configuration and access method in SAAS platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210832098.1ACN115168324A (en) | 2022-07-15 | 2022-07-15 | Database configuration and access method in SAAS platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115168324Atrue CN115168324A (en) | 2022-10-11 |
Family
ID=83495394
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210832098.1APendingCN115168324A (en) | 2022-07-15 | 2022-07-15 | Database configuration and access method in SAAS platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115168324A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103390041A (en)* | 2013-07-18 | 2013-11-13 | 杭州东信北邮信息技术有限公司 | Method and system for providing data service based on middleware |
| CN106874281A (en)* | 2015-12-11 | 2017-06-20 | 北京新媒传信科技有限公司 | Realize the method and apparatus that data base read-write is separate |
| CN114637736A (en)* | 2022-03-09 | 2022-06-17 | 北京金堤科技有限公司 | Database splitting method and device |
- 2022
- 2022-07-15CNCN202210832098.1Apatent/CN115168324A/enactivePending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103390041A (en)* | 2013-07-18 | 2013-11-13 | 杭州东信北邮信息技术有限公司 | Method and system for providing data service based on middleware |
| CN106874281A (en)* | 2015-12-11 | 2017-06-20 | 北京新媒传信科技有限公司 | Realize the method and apparatus that data base read-write is separate |
| CN114637736A (en)* | 2022-03-09 | 2022-06-17 | 北京金堤科技有限公司 | Database splitting method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11334544B2 (en) | Method, apparatus, device and medium for storing and querying data | |
| US11468027B2 (en) | Method and apparatus for providing efficient indexing and computer program included in computer readable medium therefor | |
| JP6535031B2 (en) | Data query method and apparatus | |
| US9547681B2 (en) | Combining row based and column based tables to form mixed-mode tables | |
| US11288287B2 (en) | Methods and apparatus to partition a database | |
| CN113918535B (en) | Data reading method, device, equipment and storage medium | |
| WO2018097846A1 (en) | Edge store designs for graph databases | |
| US9245003B2 (en) | Method and system for memory efficient, update optimized, transactional full-text index view maintenance | |
| CN106503040B (en) | It is applicable in the KV database and its creation method of SQL query method | |
| Matallah et al. | Experimental comparative study of NoSQL databases: HBASE versus MongoDB by YCSB | |
| US11150996B2 (en) | Method for optimizing index, master database node and subscriber database node | |
| Qi | Digital forensics and NoSQL databases | |
| US10324933B2 (en) | Technique for processing query in database management system | |
| KR20200029431A (en) | Method and apparatus for providing efficient indexing and computer program included in computer readable medium therefor | |
| CN115168324A (en) | Database configuration and access method in SAAS platform | |
| CN111104396A (en) | Cross-database data migration method and data access method | |
| US20160154812A1 (en) | Hybrid database management system | |
| US20170177670A1 (en) | Database querying apparatuses, methods for querying a database, and non-transitory tangible machine-readable media thereof | |
| CN114816247B (en) | A method and device for acquiring logical data | |
| CN111858516B (en) | Data processing method and device | |
| CN110147359B (en) | A method and device for incremental generation and a method and device for data updating | |
| CN112527911A (en) | Data storage method, device, equipment and medium | |
| JP2016149049A (en) | Information processor, information processing system, and pair data updating method and program | |
| CN117290390B (en) | Method for memory mapping on big data retrieval based on special index | |
| CN104750756B (en) | A kind of data manipulation method, equipment and metadata storage devices |
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 |