WO2020244233A1 - 一种数据存储方法及装置 - Google Patents

一种数据存储方法及装置 Download PDF

Info

Publication number
WO2020244233A1
WO2020244233A1 PCT/CN2020/071271 CN2020071271W WO2020244233A1 WO 2020244233 A1 WO2020244233 A1 WO 2020244233A1 CN 2020071271 W CN2020071271 W CN 2020071271W WO 2020244233 A1 WO2020244233 A1 WO 2020244233A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
business
domain
target
storage
Prior art date
Application number
PCT/CN2020/071271
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 创新先进技术有限公司
Priority to US16/884,444 priority Critical patent/US10970309B2/en
Publication of WO2020244233A1 publication Critical patent/WO2020244233A1/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
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/22—Indexing; Data structures therefor; Storage structures
    • 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/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Definitions

  • This application relates to the field of computer technology, in particular to a data storage method, device, computing device and storage medium.
  • the embodiments of the present application provide a data storage method, device, computing device, and storage medium to solve the technical defects in the prior art.
  • the embodiment of the application discloses a data storage method, including:
  • the method before receiving the data storage request and obtaining the to-be-stored data carrying the service domain identifier according to the data storage request, the method further includes:
  • the configuration of corresponding storage resources for each of the service domains includes:
  • the parameter information of the service domain includes data specification information
  • the configuration of corresponding storage resources for each service domain based on the parameter information of the service domain includes:
  • the basic storage resource in the storage resource is the storage resource corresponding to the business domain.
  • the parameter information of the service domain includes operation and maintenance requirement information
  • the configuration of corresponding storage resources for each service domain based on the parameter information of the service domain includes:
  • a storage resource that meets the operation and maintenance requirement of the business domain is configured for the business domain.
  • the parameter information of the service domain includes SLA service level requirement information, and the parameter information based on the service domain configures corresponding storage resources for each of the service domains, including:
  • the service domain is configured with storage resources that meet the SLA service level requirement of each sub-service in the service domain.
  • the determining the target storage resource corresponding to the data to be stored from at least two storage resources according to the business domain identifier of the data to be stored includes:
  • a storage resource corresponding to the target business domain is determined as a target storage resource.
  • the data storage method further includes:
  • the reading target data to be read based on the business domain identifier includes:
  • a data storage device includes:
  • a receiving module configured to receive a data storage request and obtain data to be stored carrying a business domain identifier according to the data storage request;
  • the determining module is configured to determine the target storage resource corresponding to the data to be stored from at least two storage resources according to the business domain identifier of the data to be stored;
  • the storage module is configured to store the data to be stored in the target storage resource.
  • the data storage device further includes:
  • the setting module is configured to set at least two business domains in advance, and set a business domain identifier for each of the business domains;
  • the configuration module is configured to configure corresponding storage resources for each of the business domains.
  • the configuration module is further configured to:
  • the parameter information of the service domain includes data specification information
  • the configuration module is further configured to:
  • the basic storage resource in the storage resource is the storage resource corresponding to the business domain.
  • the parameter information of the service domain includes operation and maintenance requirement information
  • the configuration module is further configured to:
  • a storage resource that meets the operation and maintenance requirement of the business domain is configured for the business domain.
  • the parameter information of the service domain includes SLA service level requirement information
  • the configuration module is further configured to:
  • the service domain is configured with storage resources that meet the SLA service level requirement of each sub-service in the business domain.
  • the determining module is further configured to:
  • a storage resource corresponding to the target business domain is determined as a target storage resource.
  • the data storage device further includes:
  • the reading module is configured to receive the data reading request carrying the service domain identifier and read the target data to be read.
  • the reading module is further configured to:
  • a computing device includes a memory, a processor, and computer instructions stored on the memory and running on the processor, wherein the processor implements the steps of the data storage method when the processor executes the instructions.
  • a computer-readable storage medium which stores computer instructions, which, when executed by a processor, implement the steps of the data storage method.
  • the data storage method and device provided in this application can improve the stability of various business operations in the system by dividing and isolating storage resources, enhance the flexibility of storage resource deployment and operation and maintenance, and can meet various complex services Storage requirements.
  • FIG. 1 is a schematic structural diagram of a computing device according to an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a data storage method according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a data storage method according to an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a data storage method according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a data storage method according to an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a data storage method according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a data storage device according to an embodiment of the present application.
  • first, second, etc. may be used to describe various information in one or more embodiments of this specification, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • the first may also be referred to as the second, and similarly, the second may also be referred to as the first.
  • word “if” as used herein can be interpreted as "when” or “when” or "in response to determination”.
  • Service-Level Agreement is a contract between a network service provider and a customer, which defines terms such as service type, service quality, and customer payment.
  • the SLA information may include required information such as the data type, access mode, and access performance of the data to be stored.
  • Fig. 1 is a structural block diagram of a computing device 100 according to an embodiment of the present specification.
  • the components of the computing device 100 include but are not limited to a memory 110 and a processor 120.
  • the processor 120 and the memory 110 are connected through a bus 130, and the database 150 is used to store data.
  • the computing device 100 also includes an access device 140 that enables the computing device 100 to communicate via one or more networks 160.
  • networks include public switched telephone network (PSTN), local area network (LAN), wide area network (WAN), personal area network (PAN), or a combination of communication networks such as the Internet.
  • the access device 140 may include one or more of any type of wired or wireless network interface (for example, a network interface card (NIC)), such as IEEE802.11 wireless local area network (WLAN) wireless interface, global interconnection for microwave access ( Wi-MAX) interface, Ethernet interface, universal serial bus (USB) interface, cellular network interface, Bluetooth interface, near field communication (NFC) interface, etc.
  • NIC network interface card
  • the aforementioned components of the computing device 100 and other components not shown in FIG. 1 may also be connected to each other, for example, via a bus. It should be understood that the structural block diagram of the computing device shown in FIG. 1 is for illustrative purposes only, and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.
  • the computing device 100 can be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (for example, a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (for example, a smart phone) ), wearable computing devices (for example, smart watches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or PCs.
  • a mobile computer or mobile computing device for example, a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.
  • a mobile phone for example, a smart phone
  • wearable computing devices for example, smart watches, smart glasses, etc.
  • stationary computing devices such as desktop computers or PCs.
  • the computing device 100 may also be a mobile or stationary server.
  • Fig. 2 is a schematic flowchart showing a data storage method according to an embodiment of the present application, including step S210 to step S230.
  • Step S210 Receive a data storage request and obtain the data to be stored carrying the service domain identifier according to the data storage request.
  • the data storage request may carry identification information of the data to be stored, and the identification information of the data to be stored may be the type and size of the data to be stored, which is not limited in this application.
  • the data to be stored carrying the business domain identifier is obtained.
  • the business domain identifier may be a kind of marking information indicating the characteristics or characteristics of the business domain.
  • the service domain identifier carried in the data to be stored may indicate the service domain to which the data to be stored belongs.
  • a business domain can be a domain range of a business, different business lines can correspond to different business domains, and different businesses of the same business line are all in the same business domain. For example, “paying water bills”, “paying electricity bills”, “paying gas bills” and so on all belong to different businesses of the same business line, and they all belong to the same business domain.
  • the business domain of this business domain is identified as "life payment”.
  • Step S220 According to the service domain identifier of the data to be stored, a target storage resource corresponding to the data to be stored is determined from at least two storage resources.
  • the target storage resource may be a storage resource corresponding to or matching the business domain to which the data to be stored belongs.
  • Storage resources can be various types of databases, database servers, database systems, etc., such as relational database management systems (MySql), distributed storage systems (HBase), high-performance distributed database systems that support massive amounts of data (OceanBase), Various types of databases or database systems, such as non-relational databases (NoSql), etc., may be determined according to specific circumstances, and this application does not limit this.
  • the storage resource corresponding to the business domain that is the same as the business domain identification is matched, and the storage resource is determined as the target storage resource.
  • Step S230 Store the data to be stored in the target storage resource.
  • the data to be stored may be data in various formats. Depending on the actual situation, the type of storage resource selected is different, and the data format adapted to the storage resource is also different. In the format of the data to be stored If it is compatible with the storage format of the target storage resource, the data to be stored can be directly stored in the target storage resource. If the format of the data to be stored does not match the storage format of the target storage resource In this case, the format conversion of the data to be stored can be performed first, and then the storage is performed, which is not limited in this application.
  • the stability, isolation and scalability of the system and services can be effectively improved, and storage resource deployment can be enhanced And the flexibility of operation and maintenance to meet the storage needs of various complex businesses.
  • a data storage method includes steps S310 to S360.
  • Step S310 Pre-set at least two service domains, and set a service domain identifier for each of the service domains.
  • the business domain can be a business domain range, and different business lines can correspond to the same or different business domains, depending on specific circumstances.
  • a business line may include several different businesses (sub-businesses) with at least one common attribute feature, and different businesses of the same business line are all in the same business domain.
  • the business domain identifier is a kind of marking information that indicates the characteristics or characteristics of the business domain, and the business domain identifier can be set for the business domain according to characteristic information such as the type of the business domain.
  • an application system includes two different business lines.
  • One of the business lines includes services such as “paying water bills”, “paying electricity bills”, and “paying gas bills”, all of which belong to the life payment category, and the other
  • the business lines include services such as “carriage QR code”, “code scanning and biking”, all of which belong to the traffic travel category. If the business types of the two business lines are different, the corresponding two business lines can be set respectively.
  • Business domain and set the business domain identifiers "life payment” and "traffic travel” for the two business domains.
  • an application system includes two business lines.
  • One of the business lines includes services such as “paying water bills”, “paying electricity bills”, “paying gas bills”, etc., which are all businesses in the life payment category, and the other business line Including “call charge recharge”, “broadband recharge”, “traffic recharge” and other recharge services.
  • the service types of the two business lines are “payment” and “recharge” respectively, which can belong to the same service type or It belongs to different business types, which can be determined according to actual needs.
  • business domains be divided according to the difference in business types between business lines, but also business domains can be divided according to the operation and maintenance requirements or SLA differences between business lines, depending on the specific situation. This application does not restrict this.
  • business line A has no effect on operation and maintenance and SLA.
  • business line B has special requirements for operation and maintenance, but no special requirements for SLA.
  • Step S320 Configure corresponding storage resources for each of the service domains.
  • corresponding storage resources may be configured for each service domain based on the parameter information of the service domain.
  • the parameter information of the business domain may be various information such as data specification information, operation and maintenance requirement information, SLA information, etc., depending on the specific situation, and this application does not limit this.
  • Storage resources can be various types of databases and database servers, such as relational database management system (MySql), distributed storage system (HBase), high-performance distributed database system (OceanBase) that supports massive data, and non-relational database (NoSql) and other types of databases or database systems, etc., depending on the specific situation, this application does not limit this.
  • Step S330 Receive the data storage request and obtain the data to be stored carrying the service domain identifier according to the data storage request.
  • Step S340 Determine the target storage resource corresponding to the data to be stored from at least two storage resources according to the service domain identifier of the data to be stored.
  • the business domain set with the business domain identification of the data to be stored may be determined as the target business domain according to the business domain identification of the data to be stored.
  • a storage resource corresponding to the target business domain is determined as a target storage resource.
  • the target business domain may be the business domain to which the data to be stored belongs
  • the target storage resource may be a storage resource set for the target business domain and corresponding to the target business domain.
  • the business domain of the acquired data to be stored is identified as "life payment”
  • the "life payment” business domain is determined as the target business domain
  • the storage resource corresponding to the "life payment” business domain is the target storage resource.
  • Step S350 Store the data to be stored in the target storage resource.
  • Step S360 Receive the data read request carrying the service domain identifier and read the target data to be read.
  • the target business domain to be read corresponding to the target data to be read may be determined based on the business domain identifier. Determine the target storage resource to be read based on the target business domain to be read. Read the target data to be read from the storage resource to be read.
  • the data read request may carry a business domain identifier, or may carry multiple different business domain identifiers, that is, the data read request may be issued for a single type or a single business domain of stored data , It can also be sent for a variety of different types and different business domains of stored data, depending on the specific situation, this application does not limit this.
  • the business domain to which the target data to be read belongs can be determined based on the business domain identifier, and the corresponding business domain is determined according to the business domain to which the target data to be read belongs
  • the storage resource is a target storage resource to be read, and the target data to be read is read from the target storage resource to be read.
  • the business domain corresponding to each data read request can be determined based on the two or more business domain identifiers, and each data read request is determined.
  • the storage resource corresponding to a business domain is the target storage resource to be read, and the corresponding target data to be read is read in each target storage resource to be read.
  • the data storage method described in an embodiment of the present application divides different business lines into different business domains, and sets corresponding storage resources for different business domains, which not only realizes the effective isolation of data storage and the integration of different business lines
  • the storage data does not interfere with each other, and the personalized configuration of storage resources is realized, which can meet the storage requirements of various different services. At the same time, it can also achieve fast reading of stored data, improving the stability of the system and business.
  • a data storage method includes steps S410 to S450.
  • Step S410 Pre-set at least two service domains, and set a service domain identifier for each of the service domains.
  • Step S420 Determine whether the data specification of the service domain is greater than the target specification threshold. If yes, perform step S422, if not, perform step S424.
  • Step S422 Configure storage resources that meet the data specifications of the service domain for the service domain.
  • Step S424 Determine that the basic storage resource in the storage resource is the storage resource corresponding to the service domain.
  • the number of the storage resources is at least two, and among the above at least two storage resources, at least one is a basic storage resource.
  • the data in the business domain can be directly stored To the basic storage resources, there is no need to reconfigure storage resources.
  • storage resources that conform to its capacity and other parameters can be configured for the business domain.
  • the data specification of business domain C is greater than the target capacity specification threshold. Domain C configures the corresponding storage resource C.
  • Step S430 Receive the data storage request and obtain the data to be stored carrying the service domain identifier according to the data storage request.
  • Step S440 According to the service domain identifier of the data to be stored, a target storage resource corresponding to the data to be stored is determined from at least two storage resources.
  • Step S450 Store the data to be stored in the target storage resource.
  • the data storage method described in an embodiment of the present application configures corresponding storage resources for the business domain by distinguishing the size of the business domain data specification, and the Default business domain is set, and the data specification of the business domain is less than the target threshold Next, storing the Default business domain as the target storage resource can effectively save storage space and maximize the utilization of storage resources.
  • a data storage method includes steps S510 to S550.
  • Step 510 Pre-set at least two service domains, and set a service domain identifier for each of the service domains.
  • Step S520 Based on the operation and maintenance requirement information of the service domain, configure storage resources for the service domain that meet the operation and maintenance requirements of the service domain.
  • storage resources that meet the operation and maintenance requirements of the business domain may be configured for the business domain.
  • the operation and maintenance requirements can be based on all business requirements of the virtualized network, such as the operation and maintenance operation process in the communication network, policy-based fault self-healing, policy-based automatic elastic scaling, SLA or Quality of Service (Quality of Service, QoS) ) And other automatic optimization and operation requirements.
  • the operation and maintenance requirement information may be the requirement information that the above-mentioned operation and maintenance operation based on the business domain needs to achieve corresponding to the storage resources.
  • the number of storage resources is at least two, and at least one of the storage resources is a basic storage resource.
  • the data in the business domain can be directly stored in the basic storage resource.
  • storage resources there is no need to reconfigure storage resources.
  • storage resources that meet its operation and maintenance requirements can be configured for the business domain.
  • the corresponding storage resources can be directly configured for each business domain.
  • the basic storage resources can be used as Default, which has no special requirements for operation and maintenance and SLA. Storage resources corresponding to the business domain.
  • the three business lines in an application are divided into three business domains, namely business domain A, business domain B, and Default business domain.
  • Each business domain includes one
  • determine that the basic storage resource is the storage resource corresponding to the Default business domain, and configure storage resource A and storage resource B for business domain A and business domain B to meet their operation and maintenance requirements.
  • the business domain In the case that the business domain is divided according to the business type or SLA of the business line, read the operation and maintenance requirement information of the business domain to determine whether the business domain has special requirements in operation and maintenance, and if so, configure the corresponding business domain If not, determine the basic storage resource in the storage resource as the storage resource corresponding to the business domain.
  • Other situations can be deduced by analogy, so I won't repeat them here.
  • business domain A includes two business lines.
  • Domain B and business domain C each include a business line. If business domain A has no special requirements for operation and maintenance, determine the basic storage resource as the storage resource corresponding to business domain A.
  • Business domain B and business domain C are in operation and maintenance. Both have special requirements. When the operation and maintenance requirements of business domain B and business domain C are the same, configure the same corresponding storage resource for business domain B and business domain C. In the operation and maintenance of business domain B and business domain C Under different requirements, configure corresponding storage resources for service domain B and service domain C.
  • Step S530 Receive the data storage request and obtain the data to be stored carrying the service domain identifier according to the data storage request.
  • Step S540 Determine the target storage resource corresponding to the data to be stored from at least two storage resources according to the service domain identifier of the data to be stored.
  • Step S550 Store the data to be stored in the target storage resource.
  • the business domain based on the operation and maintenance demand information of the business domain, the business domain is configured with storage resources that meet the operation and maintenance needs of the business domain, which can not only realize effective isolation of data storage , At the same time, it can meet the storage requirements of many different types of businesses and realize personalized storage.
  • a data storage method includes steps S610 to S650.
  • Step S610 Pre-set at least two service domains, and set a service domain identifier for each of the service domains.
  • Step S620 Based on the SLA information of the service domain, configure storage resources that satisfy the SLA of the service domain for the service domain.
  • the service domain may be configured with storage resources that satisfy the SLA of each sub-service in the service domain.
  • the SLA information may include required information such as the data type, access method, and access performance of the data to be stored.
  • the sub-business in the business domain includes every business on every business line in the business domain. For example, assuming that the business domain Y includes a business line m and a business line n, then the business m 1 , m 2 , m 3 ... on the business line m and the business n 1 , n 2 , n 3 ... on the business line n All of them belong to the sub-business in the business domain.
  • the number of storage resources is at least two, and at least one of the storage resources is a basic storage resource.
  • the data in the business domain can be directly stored in the basic storage In the resources, there is no need to reconfigure storage resources.
  • storage resources that conform to its SLA can be configured for the business domain.
  • corresponding storage resources can be directly configured for each service domain, wherein the storage resources corresponding to the Default service domain are basic storage resources.
  • the five business lines in an application are divided into two business domains according to the different SLAs of the business lines, namely the Default business domain and business domain A, where the Default business domain includes three business lines, business domain A If two business lines are included, the basic storage resource is determined to be the storage resource corresponding to the Default business domain, and storage resource A that meets its SLA is configured for business domain A.
  • the business domain In the case that the business domain is divided according to the business type or operation and maintenance requirements of the business domain, read the SLA of each sub-service in the business domain to determine whether the business domain has special requirements in terms of SLA, and if so, it is The storage resource corresponding to the business domain is configured. If not, it is determined that the basic storage resource in the storage resource is the storage resource corresponding to the business domain.
  • business domain A includes two business lines, business domain B
  • business domain C and business domain C each include a business line.
  • Business domain A has no special requirements in terms of SLA, and the basic storage resource is determined to be the storage resource corresponding to business domain A.
  • Both business domain B and business domain C have special requirements in terms of SLA. If the SLAs of business domain B and business domain C are the same, configure the same corresponding storage resources for business domain B and business domain C. In the case of different SLAs of business domain B and business domain C, they are Service domain B and service domain C configure corresponding storage resources.
  • Step S630 Receive the data storage request and obtain the data to be stored carrying the service domain identifier according to the data storage request.
  • Step S640 Determine the target storage resource corresponding to the data to be stored from at least two storage resources according to the service domain identifier of the data to be stored.
  • Step S650 Store the data to be stored in the target storage resource.
  • a data storage device includes:
  • the receiving module 710 is configured to receive a data storage request and obtain the to-be-stored data carrying the service domain identifier according to the data storage request.
  • the determining module 720 is configured to determine the target storage resource corresponding to the data to be stored from at least two storage resources according to the service domain identifier of the data to be stored.
  • the storage module 730 is configured to store the data to be stored in the target storage resource.
  • the data storage device further includes:
  • the setting module is configured to set at least two business domains in advance, and set a business domain identifier for each of the business domains.
  • the configuration module is configured to configure corresponding storage resources for each of the business domains.
  • the configuration module is further configured to:
  • the parameter information of the service domain includes data specification information
  • the configuration module is further configured to:
  • the storage resource that meets the data specification of the service domain is configured for the service domain.
  • the basic storage resource in the storage resource is the storage resource corresponding to the business domain.
  • the parameter information of the service domain includes operation and maintenance requirement information
  • the configuration module is further configured to:
  • a storage resource that meets the operation and maintenance requirement of the business domain is configured for the business domain.
  • the parameter information of the service domain includes SLA information, and the configuration module is further configured to.
  • the storage resource that satisfies the SLA of each sub-service in the service domain is configured for the service domain.
  • the determining module 720 is further configured to:
  • the business domain provided with the business domain identifier of the data to be stored is determined as the target business domain.
  • a storage resource corresponding to the target business domain is determined as a target storage resource.
  • the data storage device further includes:
  • the reading module is configured to receive the data reading request carrying the service domain identifier and read the target data to be read.
  • the reading module is further configured to:
  • the target business domain to be read corresponding to the target data to be read is determined based on the business domain identifier.
  • the data storage device described in an embodiment of the present application can divide business domains and personalize storage resources for different business lines, thereby improving the stability, isolation and scalability of systems and services, and enhancing storage resource deployment and operation and maintenance The flexibility to meet the storage requirements of various complex businesses.
  • An embodiment of the present application also provides a computing device, including a memory, a processor, and computer instructions stored on the memory and capable of running on the processor, and the processor implements the following steps when executing the instructions:
  • the target storage resource corresponding to the data to be stored is determined from at least two storage resources.
  • An embodiment of the present application further provides a computer-readable storage medium that stores computer instructions, which when executed by a processor, implement the steps of the data storage method described above.
  • the computer instructions include computer program codes, and the computer program codes may be in the form of source code, object code, executable files, or some intermediate forms.
  • the computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory) , Random Access Memory (RAM, Random Access Memory), electrical carrier signal, telecommunications signal, and software distribution media, etc. It should be noted that the content contained in the computer-readable medium can be appropriately added or deleted in accordance with the requirements of the legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to the legislation and patent practice, the computer-readable medium Does not include electrical carrier signals and telecommunication signals.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

一种数据存储方法及装置，涉及计算机技术领域。所述方法包括：接收数据存储请求并根据数据存储请求获取携带有业务域标识的待存储数据（S210）；根据待存储数据的业务域标识，从至少两个存储资源中确定待存储数据对应的目标存储资源（S220）；将待存储数据存储至目标存储资源（S230）。所述数据存储方法及装置，通过对存储资源进行划分隔离，可以提升系统中各种业务运行的稳定性，增强存储资源部署以及运维的灵活性，且可以满足各种复杂业务的存储需求。

Description

一种数据存储方法及装置 技术领域
本申请涉及计算机技术领域，特别涉及一种数据存储方法、装置、计算设备及存储介质。
背景技术
在计算机系统中，通常需要用到数据存储系统。随着网络应用的迅速发展，对数据存储具有访问量大、数据量大、高并发等要求，为应对突然剧增的访问量，需要扩大数据存储系统规模及改变数据存储方式。
目前，在传统的应用中，通常一个系统为多条业务线提供服务，且所有业务线的数据全部保存在同一个数据库中，但是，按照目前的方法进行数据存储，数据库一旦抖动，会影响到所有的业务，所有业务平等对待，会导致对于性能及稳定性要求较高的业务无法得到足够的保障，无法做到个性化支持和运维，且在业务发展到一定规模的情况下，易出现数据库连接池不够或容量不够的情况，扩容困难。
发明内容
有鉴于此，本申请实施例提供了一种数据存储方法、装置、计算设备及存储介质，以解决现有技术中存在的技术缺陷。
本申请实施例公开了一种数据存储方法，包括：
接收数据存储请求并根据所述数据存储请求获取携带有业务域标识的待存储数据；
根据所述待存储数据的业务域标识，从至少两个存储资源中确定所述待存储数据对应的目标存储资源；
将所述待存储数据存储至所述目标存储资源。
进一步地，在接收数据存储请求并根据所述数据存储请求获取携带有业务域标识的待存储数据之前，还包括：
预先设置至少两个业务域，并为每一个所述业务域设置业务域标识；
为每一个所述业务域配置相对应的存储资源。
进一步地，所述为每一个所述业务域配置相对应的存储资源，包括：
基于所述业务域的参数信息为每一个所述业务域配置相对应的存储资源。
进一步地，所述业务域的参数信息包括数据规格信息，所述基于所述业务域的参数信息为每一个所述业务域配置相对应的存储资源，包括：
判断所述业务域的数据规格是否大于目标规格阈值；
在所述业务域的数据规格大于目标规格阈值的情况下，为所述业务域配置满足所述业务域数据规格的存储资源；
在所述业务域的数据规格小于或等于目标规格阈值的情况下，确定所述存储资源中的基础存储资源为所述业务域相对应的存储资源。
进一步地，所述业务域的参数信息包括运维需求信息，所述基于所述业务域的参数信息为每一个所述业务域配置相对应的存储资源，包括：
基于所述业务域的运维需求信息，为所述业务域配置满足所述业务域的运维需求的存储资源。
进一步地，所述业务域的参数信息包括SLA服务等级需求信息，所述基于业务域的参数信息为每一个所述业务域配置相对应的存储资源，包括：
基于业务域中的每一个子业务的SLA服务等级需求信息，为所述业务域配置满足所述业务域中每一个子业务的SLA服务等级需求的存储资源。
进一步地，所述根据所述待存储数据的业务域标识，从至少两个存储资源中确定所述待存储数据对应的目标存储资源，包括：
根据所述待存储数据的业务域标识，确定设置有所述待存储数据的业务域标识的业务域为目标业务域；
根据所述目标业务域，确定与所述目标业务域相对应的存储资源为目标存储资源。
进一步地，所述数据存储方法，还包括：
接收携带有业务域标识的数据读取请求并读取目标待读取数据。
进一步地，所述基于业务域标识读取目标待读取数据，包括：
基于业务域标识确定所述目标待读取数据对应的目标待读取业务域；
基于所述目标待读取业务域确定目标待读取存储资源；
在所述目标待读取存储资源中读取所述目标待读取数据。
一种数据存储装置，包括：
接收模块，被配置为接收数据存储请求并根据所述数据存储请求获取携带有业务域标识的待存储数据；
确定模块，被配置为根据所述待存储数据的业务域标识，从至少两个存储资源中确定所述待存储数据对应的目标存储资源；
存储模块，被配置为将所述待存储数据存储至所述目标存储资源。
可选地，所述数据存储装置，还包括：
设置模块，被配置为预先设置至少两个业务域，并为每一个所述业务域设置业务域标识；
配置模块，被配置为为每一个所述业务域配置相对应的存储资源。
可选地，所述配置模块，进一步被配置为：
基于所述业务域的参数信息为每一个所述业务域配置相对应的存储资源。
可选地，所述业务域的参数信息包括数据规格信息，所述配置模块，进一步被配置为：
判断所述业务域的数据规格是否大于目标规格阈值；
在所述业务域的数据规格大于目标规格阈值的情况下，为所述业务域配置满足所述业务域数据规格的存储资源；
在所述业务域的数据规格小于或等于目标规格阈值的情况下，确定所述存储资源中的基础存储资源为所述业务域相对应的存储资源。
可选地，所述业务域的参数信息包括运维需求信息，所述配置模块，进一步被配置为：
基于所述业务域的运维需求信息，为所述业务域配置满足所述业务域的运维需求的存储资源。
可选地，所述业务域的参数信息包括SLA服务等级需求信息，所述配置模块，进一步被配置为：
基于业务域中的每一个子业务的SLA服务等级需求信息，为所述业务域配置满足所 述业务域中每一个子业务的SLA服务等级需求的存储资源。
可选地，所述确定模块，进一步被配置为：
根据所述待存储数据的业务域标识，确定设置有所述待存储数据的业务域标识的业务域为目标业务域；
根据所述目标业务域，确定与所述目标业务域相对应的存储资源为目标存储资源。
可选地，所述数据存储装置，还包括：
读取模块，被配置为接收携带有业务域标识的数据读取请求并读取目标待读取数据。
可选地，所述读取模块，进一步被配置为：
基于业务域标识确定所述目标待读取数据对应的目标待读取业务域；
基于所述目标待读取业务域确定目标待读取存储资源；
在所述目标待读取存储资源中读取所述目标待读取数据。
一种计算设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机指令，其特征在于，所述处理器执行所述指令时实现所述数据存储方法的步骤。
一种计算机可读存储介质，其存储有计算机指令，该指令被处理器执行时实现所述数据存储方法的步骤。
本申请提供的一种数据存储方法及装置，通过对存储资源进行划分隔离，可以提升系统中各种业务运行的稳定性，增强存储资源部署以及运维的灵活性，且可以满足各种复杂业务的存储需求。
附图说明
图1是本申请一实施例所述的计算设备的结构示意图；
图2是本申请一实施例所述的一种数据存储方法的流程示意图；
图3是本申请一实施例所述的一种数据存储方法的流程示意图；
图4是本申请一实施例所述的一种数据存储方法的流程示意图；
图5是本申请一实施例所述的一种数据存储方法的流程示意图；
图6是本申请一实施例所述的一种数据存储方法的流程示意图；
图7是本申请一实施例所述的一种数据存储装置的结构示意图。
具体实施方式
在下面的描述中阐述了很多具体细节以便于充分理解本申请。但是本申请能够以很多不同于在此描述的其它方式来实施，本领域技术人员可以在不违背本申请内涵的情况下做类似推广，因此本申请不受下面公开的具体实施的限制。
在本说明书一个或多个实施例中使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本说明书一个或多个实施例。在本说明书一个或多个实施例和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本说明书一个或多个实施例中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本说明书一个或多个实施例中可能采用术语第一、第二等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本说明书一个或多个实施例范围的情况下，第一也可以被称为第二，类似地，第二也可以被称为第一。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
首先，对本发明一个或多个实施例涉及的名词术语进行解释。
服务等级需求(Service-Level Agreement，SLA)是关于网络服务供应商和客户间的一份合同，其中定义了服务类型、服务质量和客户付款等术语。在本申请的实施例中，SLA信息可以包括待存储数据的数据类型、访问方式、访问性能等需求信息。
在本申请中，提供了一种数据存储方法、装置、计算设备及存储介质，在下面的实施例中逐一进行详细说明。
图1是示出了根据本说明书一实施例的计算设备100的结构框图。该计算设备100的部件包括但不限于存储器110和处理器120。处理器120与存储器110通过总线130相连接，数据库150用于保存数据。
计算设备100还包括接入设备140，接入设备140使得计算设备100能够经由一个或多个网络160通信。这些网络的示例包括公用交换电话网(PSTN)、局域网(LAN)、广域网(WAN)、个域网(PAN)或诸如因特网的通信网络的组合。接入设备140可以包括有线或无线的任何类型的网络接口(例如，网络接口卡(NIC))中的一个或多 个，诸如IEEE802.11无线局域网(WLAN)无线接口、全球微波互联接入(Wi-MAX)接口、以太网接口、通用串行总线(USB)接口、蜂窝网络接口、蓝牙接口、近场通信(NFC)接口，等等。
在本说明书的一个实施例中，计算设备100的上述部件以及图1中未示出的其他部件也可以彼此相连接，例如通过总线。应当理解，图1所示的计算设备结构框图仅仅是出于示例的目的，而不是对本说明书范围的限制。本领域技术人员可以根据需要，增添或替换其他部件。
计算设备100可以是任何类型的静止或移动计算设备，包括移动计算机或移动计算设备(例如，平板计算机、个人数字助理、膝上型计算机、笔记本计算机、上网本等)、移动电话(例如，智能手机)、可佩戴的计算设备(例如，智能手表、智能眼镜等)或其他类型的移动设备，或者诸如台式计算机或PC的静止计算设备。计算设备100还可以是移动式或静止式的服务器。
其中，处理器120可以执行图2所示方法中的步骤。图2是示出了根据本申请一实施例的数据存储方法的示意性流程图，包括步骤S210至步骤S230。
步骤S210：接收数据存储请求并根据所述数据存储请求获取携带有业务域标识的待存储数据。
具体地，所述数据存储请求中可以携带有待存储数据的标识信息，待存储数据的标识信息可以是待存储数据的类型、大小等，本申请对此不做限制。
根据数据存储请求中的待存储数据的标识信息，获取携带有业务域标识的待存储数据。其中，业务域标识可以是表明业务域特征或特点的一种标记信息。待存储数据中携带的业务域标识可以表示该待存储数据所属的业务域。业务域可以是一种业务的领域范围，不同的业务线可以对应不同的业务域，同一条业务线的不同业务都在同一个业务域中。例如，“缴纳水费”、“缴纳电费”、“缴纳燃气费”等等均属于同一条业务线的不同业务，均属于同一个业务域，该业务域的业务域标识为“生活缴费”。
步骤S220：根据所述待存储数据的业务域标识，从至少两个存储资源中确定所述待存储数据对应的目标存储资源。
其中，目标存储资源可以是与待存储数据所属的业务域相对应或相匹配的存储资源。存储资源可以是各种不同类型的数据库、数据库服务器、数据库系统等，如关系型数据库管理系统(MySql)、分布式存储系统(HBase)、支持海量数据的高性能分布式数 据库系统(OceanBase)、非关系型数据库(NoSql)等各种类型的数据库或数据库系统等，可视具体情况而定，本申请对此不做限制。
根据待存储数据的业务域标识，匹配与该业务域标识相同的业务域所对应的存储资源，并确定该存储资源为目标存储资源。
步骤S230：将所述待存储数据存储至所述目标存储资源。
具体地，所述待存储数据可以是各种格式的数据，根据实际情况的不同，选用的存储资源的类型的不同，存储资源相适配的数据格式也不同，在所述待存储数据的格式与目标存储资源的存储格式相适配的情况下，可以直接将所述待存储数据存储至所述目标存储资源中，在所述待存储数据的格式与目标存储资源的存储格式不适配的情况下，可以先对待存储数据进行格式转换，再进行存储，本申请对此不做限制。
本申请一实施例所述的数据存储方法，通过对存储资源进行划分，并设置至少两个单独隔离的存储资源，可以有效提升系统及业务的稳定性、隔离性及扩展性，增强存储资源部署及运维的灵活性，满足各种复杂业务的存储需求。
如图3所示，一种数据存储方法，包括步骤S310至步骤S360。
步骤S310：预先设置至少两个业务域，并为每一个所述业务域设置业务域标识。
其中，业务域可以是业务的领域范围，不同的业务线可以对应相同或不同的业务域，可视具体情况而定。一条业务线可以包括具有至少一个共同属性特点的若干个不同业务(子业务)，同一条业务线的不同业务都在同一个业务域中。业务域标识是表明业务域特征或特点的一种标记信息，可以根据业务域的类型等特征信息为业务域设置业务域标识。
例如，“付款”、“收款”和“转账”等均涉及账户资金的往来，具有共同的属性特点，是同一条业务线上的不同业务，属于同一个业务域；同样地，如“网约车司机端自动接单”和“网约车客户端打车”等均属于网约车的业务范畴，具有共同的属性特点，是同一条业务线上的不同业务，属于同一个业务域，其他情况可以此类推，在此不再赘述。
例如，假设一个应用系统中包括两条不同的业务线，其中一条业务线中包括“缴纳水费”、“缴纳电费”、“缴纳燃气费”等业务，均属于生活缴费类的业务，另一条业务线中包括“乘车二维码”、“扫码骑车”等业务，均属于交通出行类的业务，则两条业务线的业务类型不同，可以为上述两条业务线分别设置对应的业务域，且分别为两个 业务域设置业务域标识“生活缴费”和“交通出行”。
在不同的业务线的业务类型相近或相似的情况下，可以根据业务线的不同直接分别为每一条业务线设置一个业务域，也可以视具体情况对不同业务线的业务类型做类型划分，判断此两种或多种不同的业务类型是否可以看作同一种类型，若判断上述两种或多种业务类型可以看作是同一种业务类型，则为上述两种或多种业务设置同一个业务域，并为该业务域设置业务域标识，若判断上述两种或多种业务类型不可以看作是同一种业务类型，则分别为上述两种或多种业务设置相对应的业务域，并为每一个业务域设置业务域标识，本申请对此不做限制。
例如，假设一个应用系统中包括两条业务线，其中一条业务线中包括“缴纳水费”、“缴纳电费”、“缴纳燃气费”等业务，均属于生活缴费类的业务，另一条业务线中包括“话费充值”、“宽带充值”、“流量充值”等充值类的业务，两条业务线的业务类型分别为“缴费”和“充值”，即可以归属为同一种业务类型，也可以归属为不同的业务类型，具体可视实际需求确定，在设置业务域时，可以直接为“缴费”和“充值”两条业务线分别设置对应的业务域，也可以先对上述两条业务线做类型划分，在将“缴费”和“充值”归属为同一种业务类型的情况下，为两条业务线设置同一个业务域，并为该业务域设置业务域标识“缴费充值”，在将“缴费”和“充值”归属为不同的业务类型的情况下，为上述两条业务线分别设置对应的业务域，且为两个业务域分别设置业务域标识“缴费”和“充值”。
在本申请一实施例中，不仅可以根据业务线之间的业务类型的区别划分业务域，也可以根据业务线之间的运维需求或SLA的区别划分业务域，可视具体情况而定，本申请对此不做限制。
例如，假设一个应用系统中包括五条业务类型不同的业务线，分别为业务线A、业务线B、业务线C、业务线D和业务线E，其中，业务线A对运维及SLA均无特别需求，则将业务线A划分至默认(Default)业务域中，业务线B对运维具有特别需求、对SLA无特别需求，则为业务线B设置业务域Y b，业务线C对运维无特别需求，对SLA具有特别需求，则为业务线C设置业务域Y c，业务线D和业务线E对运维和SLA均具有特别需求，在业务线D和业务线E的运维需求一样、SLA不一样或运维需求不一样、SLA一样或运维需求和SLA均不一样的情况下，分别为业务线D和业务线E设置业务域Y d和业务域Y e，在业务线D和业务线E的运维需求和SLA需求均相同的情况下，为业务线D和业务线E设置同一个业务域Y de。其他情况可以此类推，此处不再 赘述。
步骤S320：为每一个所述业务域配置相对应的存储资源。
实际应用中，可以基于所述业务域的参数信息为每一个所述业务域配置相对应的存储资源。
其中，业务域的参数信息可以是数据规格信息、运维需求信息、SLA信息等各种信息，可视具体情况而定，本申请对此不做限制。存储资源可以是各种不同类型的数据库和数据库服务器，如关系型数据库管理系统(MySql)、分布式存储系统(HBase)、支持海量数据的高性能分布式数据库系统(OceanBase)、非关系型数据库(NoSql)等各种类型的数据库或数据库系统等，可视具体情况而定，本申请对此不做限制。
步骤S330：接收数据存储请求并根据所述数据存储请求获取携带有业务域标识的待存储数据。
具体可参见上述实施例，在此不再赘述。
步骤S340：根据所述待存储数据的业务域标识，从至少两个存储资源中确定所述待存储数据对应的目标存储资源。
实际应用中，可以根据所述待存储数据的业务域标识，确定设置有所述待存储数据的业务域标识的业务域为目标业务域。根据所述目标业务域，确定与所述目标业务域相对应的存储资源为目标存储资源。
具体地，目标业务域可以是待存储数据所属的业务域，目标存储资源可以是为目标业务域设置的与目标业务域相对应的存储资源。
例如，假设获取到的待存储数据的业务域标识为“生活缴费”，则确定“生活缴费”业务域为目标业务域，与“生活缴费”业务域相对应的存储资源为目标存储资源。
步骤S350：将所述待存储数据存储至所述目标存储资源。
具体可参见上述实施例，此处不再赘述。
步骤S360：接收携带有业务域标识的数据读取请求并读取目标待读取数据。
实际应用中，可以基于所述业务域标识确定所述目标待读取数据对应的目标待读取业务域。基于所述目标待读取业务域确定目标待读取存储资源。在所述待读取存储资源中读取所述目标待读取数据。
具体地，所述数据读取请求可以携带有一个业务域标识，也可以携带有多个不同的业务域标识，即所述数据读取请求可以是针对单一类型或单一业务域的存储数据发出的，也可以是针对多种不同类型、不同业务域的存储数据发出的，具体可视情况而定，本申请对此不做限制。
在所述数据读取请求仅携带有一个业务域标识的情况下，可以基于该业务域标识，确定目标待读取数据所属的业务域，根据目标待读取数据所属的业务域，确定对应的存储资源为目标待读取存储资源，并在该目标待读取存储资源中读取目标待读取数据。
在所述数据读取请求携带有两个或多个业务域标识的情况下，可以基于上述两个或多个业务域标识，分别确定每一个数据读取请求所对应的业务域，并确定每一个业务域所对应的存储资源为目标待读取存储资源，并在每一个目标待读取存储资源中读取对应的目标待读取数据。
本申请一实施例所述的数据存储方法，通过对不同的业务线划分不同的业务域，并为不同的业务域分别设置对应的存储资源，不仅实现了数据存储的有效隔离、不同业务线的存储数据之间互不干扰，且实现了存储资源的个性化配置，可以满足各种不同业务的存储需求。同时，还可以实现对已存储数据的快速读取，提升系统及业务的稳定性。
如图4所示，一种数据存储方法，包括步骤S410至步骤S450。
步骤S410：预先设置至少两个业务域，并为每一个所述业务域设置业务域标识。
具体可参见上述实施例，此处不再赘述。
步骤S420：判断所述业务域的数据规格是否大于目标规格阈值。若是，则执行步骤S422，若否，则执行步骤S424。
步骤S422：为所述业务域配置满足所述业务域数据规格的存储资源。
步骤S424：确定所述存储资源中的基础存储资源为所述业务域相对应的存储资源。
具体地，所述存储资源的数量至少为两个，且在上述至少两个存储资源中，至少一个为基础存储资源，对于数据规格较小的业务域，可以将该业务域中的数据直接存储至基础存储资源中，无需再重新配置存储资源。对于数据规格较大的业务域，可以为该业务域配置与其容量大小等参数均相符合的存储资源。
例如，假设一个应用程序包括业务域A、业务域B、业务域C三个业务域，预 先设置目标容量规格阈值为xGB，其中，业务域A的数据规格为aGB，业务域B的数据规格为bGB，业务域C的数据规格为cGB，c＞x＝a＞b，业务域A的数据规格与预先设置的目标容量规格阈值相等，确定存储资源中的基础存储资源为业务域A相对应的存储资源，业务域B的数据规格小于预先设置的目标容量规格阈值，确定存储资源中的基础存储资源为业务域B相对应的存储资源，业务域C的数据规格大于目标容量规格阈值，为业务域C配置相对应的存储资源C。
步骤S430：接收数据存储请求并根据所述数据存储请求获取携带有业务域标识的待存储数据。
具体可参见上述实施例，此处不再赘述。
步骤S440：根据所述待存储数据的业务域标识，从至少两个存储资源中确定所述待存储数据对应的目标存储资源。
具体可参见上述实施例，此处不再赘述。
步骤S450：将所述待存储数据存储至所述目标存储资源。
具体可参见上述实施例，此处不再赘述。
本申请一实施例所述的数据存储方法，通过区分业务域数据规格的大小来为业务域配置相对应的存储资源，且设置有Default业务域，并在业务域的数据规格小于目标阈值的情况下，将Default业务域作为目标存储资源进行存储，可以有效节省存储空间，实现存储资源的利用最大化。
如图5所示，一种数据存储方法，包括步骤S510至步骤S550。
步骤510：预先设置至少两个业务域，并为每一个所述业务域设置业务域标识。
具体可参见上述实施例，此处不再赘述。
步骤S520：基于所述业务域的运维需求信息，为所述业务域配置满足所述业务域的运维需求的存储资源。
实际应用中，可以基于所述业务域的运维需求信息，为所述业务域配置满足所述业务域的运维需求的存储资源。
其中，运维需求可以是基于虚拟化网络的所有业务需求，例如通信网络中的运维操作流程、基于策略的故障自愈、基于策略自动弹性伸缩、基于SLA或服务质量(Quality of Service，QoS)等的自动优化等的运维操作需求。运维需求信息可以是基于 业务域的上述运维操作对于存储资源的相对应所需要达到的需求信息。
具体地，所述存储资源的数量至少为两个，且其中的至少一个存储资源为基础存储资源，对于在运维方面无特别需求的业务域，可以将该业务域中的数据直接存储至基础存储资源中，无需再重新配置存储资源。对于在运维方面有特别需求的业务域，可以为该业务域配置与其运维需求相符合的存储资源。
在所述业务域为根据业务线的运维需求划分的情况下，可以直接为每一个业务域配置相对应的存储资源，其中，基础存储资源可以作为对运维、SLA均无特别需求的Default业务域对应的存储资源。
例如，根据业务线的运维需求的不同将一个应用程序中的三条业务线划分为三个业务域，分别为业务域A、业务域B和Default业务域，其中，每个业务域分别包括一条业务线，则确定基础存储资源为Default业务域对应的存储资源，且分别为业务域A和业务域B配置满足其运维需求的存储资源A和存储资源B。
在所述业务域为根据业务线的业务类型或SLA划分情况下，读取业务域的运维需求信息，判断该业务域在运维方面是否具有特别需求，若是，则为该业务域配置相应的存储资源，若否，则确定存储资源中的基础存储资源为该业务域相对应的存储资源。其他情况可以此类推，在此不再赘述。
例如，假设根据业务类型的不同将一个应用程序中的四条业务线划分为三个业务域，分别为业务域A、业务域B和业务域C，其中业务域A中包括两条业务线，业务域B和业务域C中各包括一条业务线，业务域A在运维方面无特别需求，则确定基础存储资源为业务域A相对应的存储资源，业务域B和业务域C在运维方面均具有特别需求，在业务域B和业务域C的运维需求相同的情况下，为业务域B和业务域C配置同一个相对应的存储资源，在业务域B和业务域C的运维需求不同的情况下，分别为业务域B和业务域C配置相对应的存储资源。
步骤S530：接收数据存储请求并根据所述数据存储请求获取携带有业务域标识的待存储数据。
具体可参见上述实施例，此处不再赘述。
步骤S540：根据所述待存储数据的业务域标识，从至少两个存储资源中确定所述待存储数据对应的目标存储资源。
具体可参见上述实施例，此处不再赘述。
步骤S550：将所述待存储数据存储至所述目标存储资源。
具体可参见上述实施例，此处不再赘述。
本申请一实施例所述的数据存储方法，基于所述业务域的运维需求信息，为所述业务域配置满足所述业务域的运维需求的存储资源，不仅可以实现数据存储的有效隔离，同时可以满足多种不同类型的业务对于存储的需求，实现个性化存储。
如图6所示，一种数据存储方法，包括步骤S610至步骤S650。
步骤S610：预先设置至少两个业务域，并为每一个所述业务域设置业务域标识。
具体可参见上述实施例，此处不再赘述。
步骤S620：基于所述业务域的SLA信息，为所述业务域配置满足所述业务域的SLA的存储资源。
实际应用中，可以基于业务域中的每一个子业务的SLA信息，为所述业务域配置满足所述业务域中每一个子业务的SLA的存储资源。
其中，SLA信息可以包括待存储数据的数据类型、访问方式、访问性能等需求信息。业务域中的子业务包括该业务域中每一条业务线上的每一个业务。例如，假设业务域Y中包括业务线m和业务线n，则业务线m上的业务m 1、m 2、m 3……以及业务线n上的业务n 1、n 2、n 3……等均属于该业务域中的子业务。
具体地，所述存储资源的数量至少为两个，且其中的至少一个存储资源为基础存储资源，对于在SLA方面无特别需求的业务域，可以将该业务域中的数据直接存储至基础存储资源中，无需再重新配置存储资源。对于在SLA方面有特别需求的业务域，可以为该业务域配置与其SLA相符合的存储资源。
在所述业务域为根据业务域的SLA划分的情况下，可以直接为每一个业务域配置相对应的存储资源，其中，Default业务域对应的存储资源为基础存储资源。
例如，假设根据业务线的SLA的不同将一个应用程序中的五条业务线划分为两个业务域，分别为Default业务域和业务域A，其中，Default业务域中包括三条业务线，业务域A中包括两条业务线，则确定基础存储资源为Default业务域对应的存储资源，并为业务域A配置满足其SLA的存储资源A。
在所述业务域为根据业务域的业务类型或运维需求划分的情况下，读取业务域中每一个子业务的SLA，判断该业务域在SLA方面是否具有特别需求，若是，则为该 业务域配置相对应的存储资源，若否，则确定存储资源中的基础存储资源为该业务域相对应的存储资源。
假设根据业务类型的不同将一个应用程序中的四条业务线划分为三个业务域，分别为业务域A、业务域B和业务域C，其中业务域A中包括两条业务线，业务域B和业务域C中各包括一条业务线，业务域A在SLA方面无特别需求，则确定基础存储资源为业务域A相对应的存储资源，业务域B和业务域C在SLA方面均具有特别需求，在业务域B和业务域C的SLA相同的情况下，为业务域B和业务域C配置同一个相对应的存储资源，在业务域B和业务域C的SLA不同的情况下，分别为业务域B和业务域C配置相对应的存储资源。
步骤S630：接收数据存储请求并根据所述数据存储请求获取携带有业务域标识的待存储数据。
具体可参见上述实施例，此处不再赘述。
步骤S640：根据所述待存储数据的业务域标识，从至少两个存储资源中确定所述待存储数据对应的目标存储资源。
具体可参见上述实施例，此处不再赘述。
步骤S650：将所述待存储数据存储至所述目标存储资源。
具体可参见上述实施例，此处不再赘述。
本申请一实施例所述的数据存储方法，基于业务域中的每一个子业务的SLA，为所述业务域配置满足所述业务域中每一个子业务的SLA的存储资源，可以实现存储资源的个性化配置，满足各种复杂业务的存储需求。
如图7所示，一种数据存储装置，包括：
接收模块710，被配置为接收数据存储请求并根据所述数据存储请求获取携带有业务域标识的待存储数据。
确定模块720，被配置为根据所述待存储数据的业务域标识，从至少两个存储资源中确定所述待存储数据对应的目标存储资源。
存储模块730，被配置为将所述待存储数据存储至所述目标存储资源。
可选地，所述数据存储装置，还包括：
设置模块，被配置为预先设置至少两个业务域，并为每一个所述业务域设置业务域标识。
配置模块，被配置为为每一个所述业务域配置相对应的存储资源。
可选地，所述配置模块，进一步被配置为：
基于所述业务域的参数信息为每一个所述业务域配置相对应的存储资源。
可选地，所述业务域的参数信息包括数据规格信息，所述配置模块，进一步被配置为：
判断所述业务域的数据规格是否大于目标规格阈值。
在所述业务域的数据规格大于目标规格阈值的情况下，为所述业务域配置满足所述业务域数据规格的存储资源。
在所述业务域的数据规格小于或等于目标规格阈值的情况下，确定所述存储资源中的基础存储资源为所述业务域相对应的存储资源。
可选地，所述业务域的参数信息包括运维需求信息，所述配置模块，进一步被配置为：
基于所述业务域的运维需求信息，为所述业务域配置满足所述业务域的运维需求的存储资源。
可选地，所述业务域的参数信息包括SLA信息，所述配置模块，进一步被配置为。
基于业务域中的每一个子业务的SLA信息，为所述业务域配置满足所述业务域中每一个子业务的SLA的存储资源。
可选地，所述确定模块720，进一步被配置为：
根据所述待存储数据的业务域标识，确定设置有所述待存储数据的业务域标识的业务域为目标业务域。
根据所述目标业务域，确定与所述目标业务域相对应的存储资源为目标存储资源。
可选地，所述数据存储装置，还包括：
读取模块，被配置为接收携带有业务域标识的数据读取请求并读取目标待读取 数据。
可选地，所述读取模块，进一步被配置为：
基于业务域标识确定所述目标待读取数据对应的目标待读取业务域。
基于所述目标待读取业务域确定目标待读取存储资源。
在所述目标待读取存储资源中读取所述目标待读取数据。
本申请一实施例所述的数据存储装置，可以对不同的业务线划分业务域并个性化配置存储资源，进而提升系统及业务的稳定性、隔离性及扩展性，增强存储资源部署及运维的灵活性，满足各种复杂业务的存储需求。
本申请一实施例还提供一种计算设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机指令，所述处理器执行所述指令时实现以下步骤：
接收数据存储请求并根据所述数据存储请求获取携带有业务域标识的待存储数据。
根据所述待存储数据的业务域标识，从至少两个存储资源中确定所述待存储数据对应的目标存储资源。
将所述待存储数据存储至所述目标存储资源。
本申请一实施例还提供一种计算机可读存储介质，其存储有计算机指令，该指令被处理器执行时实现如前所述数据存储方法的步骤。
上述为本实施例的一种计算机可读存储介质的示意性方案。需要说明的是，该存储介质的技术方案与上述的数据存储方法的技术方案属于同一构思，存储介质的技术方案未详细描述的细节内容，均可以参见上述数据存储方法的技术方案的描述。
所述计算机指令包括计算机程序代码，所述计算机程序代码可以为源代码形式、对象代码形式、可执行文件或某些中间形式等。所述计算机可读介质可以包括：能够携带所述计算机程序代码的任何实体或装置、记录介质、U盘、移动硬盘、磁碟、光盘、计算机存储器、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、电载波信号、电信信号以及软件分发介质等。需要说明的是，所述计算机可读介质包含的内容可以根据司法管辖区内立法和专利实践的要求进行适当的增减，例如在某些司法管辖区，根据立法和专利实践，计算机可读介质不包括电载波信号和电信信号。
需要说明的是，对于前述的各方法实施例，为了简便描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本申请并不受所描述的动作顺序的限制，因为依据本申请，某些步骤可以采用其它顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定都是本申请所必须的。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其它实施例的相关描述。
以上公开的本申请优选实施例只是用于帮助阐述本申请。可选实施例并没有详尽叙述所有的细节，也不限制该发明仅为所述的具体实施方式。显然，根据本说明书的内容，可作很多的修改和变化。本说明书选取并具体描述这些实施例，是为了更好地解释本申请的原理和实际应用，从而使所属技术领域技术人员能很好地理解和利用本申请。本申请仅受权利要求书及其全部范围和等效物的限制。

Claims (20)

  1. 一种数据存储方法，其特征在于，包括：
    接收数据存储请求并根据所述数据存储请求获取携带有业务域标识的待存储数据；
    根据所述待存储数据的业务域标识，从至少两个存储资源中确定所述待存储数据对应的目标存储资源；
    将所述待存储数据存储至所述目标存储资源。
  2. 根据权利要求1所述的数据存储方法，其特征在于，所述接收数据存储请求并根据所述数据存储请求获取携带有业务域标识的待存储数据之前，还包括：
    预先设置至少两个业务域，并为每一个所述业务域设置业务域标识；
    为每一个所述业务域配置相对应的存储资源。
  3. 根据权利要求2所述的数据存储方法，其特征在于，所述为每一个所述业务域配置相对应的存储资源，包括：
    基于所述业务域的参数信息为每一个所述业务域配置相对应的存储资源。
  4. 根据权利要求3所述的数据存储方法，其特征在于，所述业务域的参数信息包括数据规格信息，所述基于所述业务域的参数信息为每一个所述业务域配置相对应的存储资源，包括：
    判断所述业务域的数据规格是否大于目标规格阈值；
    在所述业务域的数据规格大于目标规格阈值的情况下，为所述业务域配置满足所述业务域数据规格的存储资源；
    在所述业务域的数据规格小于或等于目标规格阈值的情况下，确定所述存储资源中的基础存储资源为所述业务域相对应的存储资源。
  5. 根据权利要求3所述的数据存储方法，其特征在于，所述业务域的参数信息包括运维需求信息，所述基于所述业务域的参数信息为每一个所述业务域配置相对应的存储资源，包括：
    基于所述业务域的运维需求信息，为所述业务域配置满足所述业务域的运维需求的存储资源。
  6. 根据权利要求3所述的数据存储方法，其特征在于，所述业务域的参数信息包括SLA服务等级需求信息，所述基于业务域的参数信息为每一个所述业务域配置相对应的存储资源，包括：
    基于业务域中的每一个子业务的SLA服务等级需求信息，为所述业务域配置满足所述业务域中每一个子业务的SLA服务等级需求的存储资源。
  7. 根据权利要求2所述的数据存储方法，其特征在于，所述根据所述待存储数据的业务域标识，从至少两个存储资源中确定所述待存储数据对应的目标存储资源，包括：
    根据所述待存储数据的业务域标识，确定设置有所述待存储数据的业务域标识的业务域为目标业务域；
    根据所述目标业务域，确定与所述目标业务域相对应的存储资源为目标存储资源。
  8. 根据权利要求1所述的数据存储方法，其特征在于，还包括：
    接收携带有业务域标识的数据读取请求并读取目标待读取数据。
  9. 根据权利要求8所述的数据存储方法，其特征在于，所述基于业务域标识读取目标待读取数据，包括：
    基于所述业务域标识确定所述目标待读取数据对应的目标待读取业务域；
    基于所述目标待读取业务域确定目标待读取存储资源；
    在所述目标待读取存储资源中读取所述目标待读取数据。
  10. 一种数据存储装置，其特征在于，包括：
    接收模块，被配置为接收数据存储请求并根据所述数据存储请求获取携带有业务域标识的待存储数据；
    确定模块，被配置为根据所述待存储数据的业务域标识，从至少两个存储资源中确定所述待存储数据对应的目标存储资源；
    存储模块，被配置为将所述待存储数据存储至所述目标存储资源。
  11. 根据权利要求10所述的数据存储装置，其特征在于，还包括：
    设置模块，被配置为预先设置至少两个业务域，并为每一个所述业务域设置业务域标识；
    配置模块，被配置为为每一个所述业务域配置相对应的存储资源。
  12. 根据权利要求11所述的数据存储装置，其特征在于，所述配置模块，进一步被配置为：
    基于所述业务域的参数信息为每一个所述业务域配置相对应的存储资源。
  13. 根据权利要求12所述的数据存储装置，其特征在于，所述业务域的参数信息包括数据规格信息，所述配置模块，进一步被配置为：
    判断所述业务域的数据规格是否大于目标规格阈值；
    在所述业务域的数据规格大于目标规格阈值的情况下，为所述业务域配置满足所述业务域数据规格的存储资源；
    在所述业务域的数据规格小于或等于目标规格阈值的情况下，确定所述存储资源中 的基础存储资源为所述业务域相对应的存储资源。
  14. 根据权利要求12所述的数据存储装置，其特征在于，所述业务域的参数信息包括运维需求信息，所述配置模块，进一步被配置为：
    基于所述业务域的运维需求信息，为所述业务域配置满足所述业务域的运维需求的存储资源。
  15. 根据权利要求12所述的数据存储装置，其特征在于，所述业务域的参数信息包括SLA服务等级需求信息，所述配置模块，进一步被配置为：
    基于业务域中的每一个子业务的SLA服务等级需求信息，为所述业务域配置满足所述业务域中每一个子业务的SLA服务等级需求的存储资源。
  16. 根据权利要求11所述的数据存储装置，其特征在于，所述确定模块，进一步被配置为：
    根据所述待存储数据的业务域标识，确定设置有所述待存储数据的业务域标识的业务域为目标业务域；
    根据所述目标业务域，确定与所述目标业务域相对应的存储资源为目标存储资源。
  17. 根据权利要求10所述的数据存储装置，其特征在于，还包括：
    读取模块，被配置为接收携带有业务域标识的数据读取请求并读取目标待读取数据。
  18. 根据权利要求17所述的数据存储装置，其特征在于，所述读取模块，进一步被配置为：
    基于所述业务域标识确定所述目标待读取数据对应的目标待读取业务域；
    基于所述目标待读取业务域确定目标待读取存储资源；
    在所述目标待读取存储资源中读取所述目标待读取数据。
  19. 一种计算设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机指令，其特征在于，所述处理器执行所述指令时实现权利要求1-9任意一项所述方法的步骤。
  20. 一种计算机可读存储介质，其存储有计算机指令，其特征在于，该指令被处理器执行时实现权利要求1-9任意一项所述方法的步骤。
PCT/CN2020/071271 2019-06-05 2020-01-10 一种数据存储方法及装置 WO2020244233A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/884,444 US10970309B2 (en) 2019-06-05 2020-05-27 Data storage method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910487832.3A CN110347675A (zh) 2019-06-05 2019-06-05 一种数据存储方法及装置
CN201910487832.3 2019-06-05

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/884,444 Continuation US10970309B2 (en) 2019-06-05 2020-05-27 Data storage method and apparatus

Publications (1)

Publication Number Publication Date
WO2020244233A1 true WO2020244233A1 (zh) 2020-12-10

Family

ID=68181555

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/071271 WO2020244233A1 (zh) 2019-06-05 2020-01-10 一种数据存储方法及装置

Country Status (2)

Country Link
CN (1) CN110347675A (zh)
WO (1) WO2020244233A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10970309B2 (en) 2019-06-05 2021-04-06 Advanced New Technologies Co., Ltd. Data storage method and apparatus
CN110347675A (zh) * 2019-06-05 2019-10-18 阿里巴巴集团控股有限公司 一种数据存储方法及装置
CN111756828B (zh) * 2020-06-19 2023-07-14 广东浪潮大数据研究有限公司 一种数据存储方法、装置及设备
CN111901352B (zh) * 2020-07-30 2023-08-25 彩讯科技股份有限公司 消息分发处理的方法、装置、服务器及存储介质
CN113031858B (zh) * 2021-02-10 2022-09-20 山东英信计算机技术有限公司 一种基于多双活存储的数据处理方法、系统及介质
CN116627356B (zh) * 2023-07-21 2023-11-14 江苏华存电子科技有限公司 一种大容量存储数据的分布控制方法及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140280382A1 (en) * 2013-03-12 2014-09-18 Netapp, Inc. Capacity accounting for heterogeneous storage systems
CN104468737A (zh) * 2013-12-13 2015-03-25 浪潮(北京)电子信息产业有限公司 一种基于业务类别特征的存储分级调度方法及系统
CN108681578A (zh) * 2018-05-10 2018-10-19 腾讯科技（深圳）有限公司 一种业务数据存储方法、装置、服务器及存储介质
CN109325200A (zh) * 2018-07-25 2019-02-12 北京京东尚科信息技术有限公司 获取数据的方法、装置及计算机可读存储介质
CN110347675A (zh) * 2019-06-05 2019-10-18 阿里巴巴集团控股有限公司 一种数据存储方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7546486B2 (en) * 2006-08-28 2009-06-09 Bycast Inc. Scalable distributed object management in a distributed fixed content storage system
CN107766343B (zh) * 2016-08-15 2022-02-25 华为技术有限公司 一种数据存储方法、装置及存储服务器
CN107566505A (zh) * 2017-09-15 2018-01-09 郑州云海信息技术有限公司 数据存储资源管理方法、主节点、系统、装置及存储介质
CN109542961B (zh) * 2018-10-19 2024-05-03 中国平安财产保险股份有限公司 数据存储方法、装置、计算机设备和存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140280382A1 (en) * 2013-03-12 2014-09-18 Netapp, Inc. Capacity accounting for heterogeneous storage systems
CN104468737A (zh) * 2013-12-13 2015-03-25 浪潮(北京)电子信息产业有限公司 一种基于业务类别特征的存储分级调度方法及系统
CN108681578A (zh) * 2018-05-10 2018-10-19 腾讯科技（深圳）有限公司 一种业务数据存储方法、装置、服务器及存储介质
CN109325200A (zh) * 2018-07-25 2019-02-12 北京京东尚科信息技术有限公司 获取数据的方法、装置及计算机可读存储介质
CN110347675A (zh) * 2019-06-05 2019-10-18 阿里巴巴集团控股有限公司 一种数据存储方法及装置

Also Published As

Publication number Publication date
CN110347675A (zh) 2019-10-18

Similar Documents

Publication Publication Date Title
WO2020244233A1 (zh) 一种数据存储方法及装置
EP3512233B1 (en) Method for managing network slice and management unit
US10970309B2 (en) Data storage method and apparatus
US20090274094A1 (en) Advertising support for a plurality of service networks by a wireless access point
US11070433B2 (en) Network function NF management method and NF management device
US11595473B2 (en) Ad hoc decentralized cloud infrastructure
CN111538605B (zh) 一种分布式数据访问层中间件及命令执行方法和装置
WO2021082649A1 (zh) 榜单更新方法、装置、可读介质和电子设备
CN111343241B (zh) 一种图数据更新方法、装置及系统
CN112764920A (zh) 一种边缘应用部署方法、装置、设备和存储介质
CN110737425A (zh) 一种计费平台系统的应用程序的建立方法及装置
CN109753424B (zh) Ab测试的方法和装置
CN112686528A (zh) 用于分配客服资源的方法、装置、服务器和介质
CN106713353A (zh) 一种地理信息服务的智能化无缝聚合方法及系统
CN114036031B (zh) 一种企业数字中台中资源服务应用的调度系统和方法
CN111066333A (zh) 能获取esim配置文件的装置
WO2022062981A1 (zh) 资源调度方法和系统、电子设备及计算机可读存储介质
WO2022057727A1 (zh) 网络质量确定方法、装置、电子设备和可读存储介质
CN114595167A (zh) 分布式缓存系统、方法以及装置
US11405766B2 (en) Connecting computer processing systems and transmitting data
US20210250962A1 (en) Connecting computer processing systems and transmitting data
CN111666097A (zh) 基于业务场景的能力显性化方法和装置
US20170364293A1 (en) Method and apparatus for data processing
US20210385634A1 (en) Method of determining shared service index based on shared service of communication credential
CN115423030A (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: 20818782

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: 20818782

Country of ref document: EP

Kind code of ref document: A1