WO2023106492A1

WO2023106492A1 - Operation method for data serving structure configuration and electronic device for supporting same

Info

Publication number: WO2023106492A1
Application number: PCT/KR2021/019120
Authority: WO
Inventors: 카델프라카쉬; 김두형; 김기현; 김태일
Original assignee: 쿠팡 주식회사
Priority date: 2021-12-08
Filing date: 2021-12-15
Publication date: 2023-06-15
Also published as: KR20230086558A; KR102403609B1; TW202324093A

Abstract

Disclosed is a method for configuring a data serving structure by an electronic device providing a service, the method including the steps of: identifying information on a frontend including a plurality of customer page domains for the service and information on a backend including a plurality of backend data domains related to a database for the service; acquiring configuration information for configuring a data serving structure between the frontend and the backend; and configuring the data serving structure including a main data serving structure for serving data requested from the frontend, on the basis of the configuration information.

Description

Operation method for setting data serving structure and electronic device supporting the same

The present invention relates to a method and apparatus for setting a data serving structure, and more particularly, to a method and an electronic device for setting a data serving structure based on a serving structure selectively applicable for data serving. will be.

With the development of electronic technology, e-commerce has become a part of shopping. Customers can purchase products online without going directly to a shopping mall or market, and the products purchased online are delivered to the delivery address requested by the customer.

In the case of e-commerce, since the provision of detailed and accurate information about products has a significant impact on service satisfaction, various methods for providing more detailed and accurate information are being discussed.

In this regard, reference may be made to prior literature such as KR101756594B1 or KR101500849B1.

According to the method of the present invention, an electronic device setting a data serving structure may selectively set a data serving structure based on an applicable serving structure.

The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the description below. You will be able to.

Various embodiments may provide an operating method of an electronic device for setting a data serving structure and an electronic device supporting the same.

In a method for setting a data serving structure by an electronic device providing a service according to various embodiments, information on a frontend including a plurality of customer page domains for the service and the service verifying information about a backend including a plurality of backend data domains related to a database for a data base; obtaining setting information for setting a data serving structure between the front end and the back end; and setting the data serving structure including a main data serving structure for serving data requested by the front end, based on the setting information.

In an exemplary embodiment, the setting information includes main setting information for setting the main data serving structure, and the main data serving structure includes: a plurality of data queues corresponding to the plurality of backend data domains; Storage for storing data transmitted through the plurality of data queues; and a serving layer that calls the requested data from the storage and transmits it to the front end.

In an exemplary embodiment, the setting information may include first additional setting information for setting a first additional data serving structure added to the main data serving structure or a second additional data serving structure added to the main data serving structure. It may further include second additional setting information for setting .

In an exemplary embodiment, the first additional data serving structure may include: a cache acquiring and storing at least some data included in data stored in the storage from the storage; an update data queue configured to transmit the updated first data to the cache when updated first data corresponding to the first data included in the at least some data is identified in the storage; and a cache update manager for managing transmission of the updated first data to the cache through the update data queue, wherein the second additional data serving structure determines that real-time update is required among data stored in the database. A real time cache for acquiring and storing real-time updated second data corresponding to the second data through a specific data queue related to the second data among the plurality of data queues; and a real-time cache update manager that manages to transmit the real-time updated second data to the real-time cache through the specific data queue.

In an exemplary embodiment, the setting information may include information for interworking the first supplementary data serving structure and the second supplementary data serving structure with the main data serving structure.

In an exemplary embodiment, the updated first data is a data queue related to the first data among the plurality of data queues based on a first cycle corresponding to an update cycle of the storage when the first data is updated. and when the updated first data is confirmed in the storage and the update data queue according to the first period, the cache update manager operates the updated first data through the update data queue. It may be directed to transfer data to the cache.

In an exemplary embodiment, the setting of the data serving structure may include setting the data serving structure including the main data serving structure and the first additional data serving structure based on the first additional setting information. Including, the serving layer preferentially calls the requested data from the cache and transmits it to the front-end, and when the requested data is not checked in the cache, the serving layer retrieves the requested data from the cache. It can be called from storage and transmitted to the front end.

In an exemplary embodiment, the at least some of the data stored in the cache is selected to be stored in the cache based on a data call priority among data stored in the storage, and the data call priority is selected to be stored in the data call from the serving layer. It can be determined based on the number of times.

In an exemplary embodiment, when the updated first data is identified in the storage and the first data not updated in the cache is identified, update request information for the first data is transmitted by the serving layer. can

In an exemplary embodiment, the second data updated in real time may be transmitted to the real time cache through the specific data queue based on a second period corresponding to real time when the second data is updated.

In an exemplary embodiment, the setting of the data serving structure may include setting the data serving structure including the main data serving structure and the second additional data serving structure based on the second additional setting information. and, based on whether the requested data corresponds to data requiring real-time updating, the serving layer may call the requested data from the real-time cache and transmit the requested data to the front-end.

In an exemplary embodiment, the setting of the data serving structure may include the main data serving structure, the first additional data serving structure, and the second additional setting information based on the first additional setting information and the second additional setting information. and setting the data serving structure to include an additional data serving structure, wherein when the requested data corresponds to data requiring real-time updating, the serving layer transmits the requested data to both the cache and the real-time cache. The latest data among the data called by the serving layer in the cache and the real-time cache may be transmitted to the front end.

In an exemplary embodiment, when the requested data does not correspond to data requiring real-time update, the serving layer may call the requested data from the cache and transmit the requested data to the front end.

In an exemplary embodiment, the method may further include acquiring information about whether the requested data corresponds to data requiring real-time updating.

In an exemplary embodiment, when the front end requests a data set including a plurality of data and the requested data is included in the plurality of data, all of the plurality of data is stored in the storage, the cache, or the real-time cache. The requested data may be transmitted to the front end based on a point called by the serving layer in

In an exemplary embodiment, it is confirmed that identification information corresponding to the data set is set for the plurality of data, and all of the plurality of data is called from the storage, the cache, or the real-time cache based on the identification information It can be.

In an exemplary embodiment, the obtaining of setting information may include checking information on a first service domain related to the service; checking information on one or more backend data domains related to the first service domain among the plurality of backend data domains; checking first information on whether or not the first additional data serving structure needs to be set and second information about whether or not the second additional data serving structure needs to be set, based on the information on the one or more backend data; and acquiring the setting information determined to include the first additional setting information or the second additional setting information based on the first information and the second information.

In an exemplary embodiment, the requested data may be requested from a first customer page corresponding to a first customer page domain included in the plurality of customer page domains.

An electronic device for setting a data serving structure related to a service according to various embodiments, comprising: a processor; and one or more memories storing one or more instructions, which, when executed, cause the processor to: ) and checking information about a backend including a plurality of backend data domains related to a database for the service; obtaining setting information for setting a data serving structure between the front end and the back end; and setting the data serving structure including the main data serving structure for serving the data requested by the front end based on the setting information.

The various embodiments of the present disclosure described above are only some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the various embodiments of the present disclosure can be made by those skilled in the art. It can be derived and understood based on the detailed description to be described below.

The present invention provides a method for setting a data serving structure based on a serving structure that is selectively applicable to an electronic device that sets a data serving structure, thereby reducing processing delay for data serving and optimizing data serving. have an effect

The effects obtainable in the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by those skilled in the art from the description below. will be.

1 is a diagram for explaining a data serving structure setting system in which a method of operating an electronic device for setting a data serving structure according to various embodiments may be implemented.

2 is a diagram illustrating configurations of a server device and a device interlocked with the server device according to various embodiments.

3 is a diagram illustrating an operating method of the server device 100 for setting a data serving structure according to various embodiments.

FIG. 4 is a diagram showing an overview of data flow related to data serving of a front end and a back end related to a service.

5 is a diagram showing how a main data serving structure is set between a front end and a back end.

6 is a diagram showing how a first additional data serving structure is added and configured between a front end and a back end.

FIG. 7 is a diagram showing how a second additional data serving structure is added and set between a front end and a back end.

FIG. 8 is a diagram illustrating how a first additional data serving structure and a second additional data serving structure are added and configured between a front end and a back end.

FIG. 9 is a diagram illustrating an operation method of acquiring setting information by the server device 100 for setting a data serving structure according to various embodiments.

10 is a diagram illustrating an example of setting a data serving structure according to a backend data domain corresponding to a service domain.

11 is a diagram illustrating a state in which a plurality of data serving structures are set between a front end and a back end.

The following embodiments combine elements and features of various embodiments in a predetermined form. Each component or feature may be considered optional unless explicitly stated otherwise. Each component or feature may be implemented in a form not combined with other components or features. In addition, various embodiments may be configured by combining some components and features. The order of operations described in various embodiments may be changed. Some components or features of one embodiment may be included in another embodiment, or may be replaced with corresponding components or features of another embodiment.

In the description of the drawings, procedures or steps that may obscure the gist of various embodiments are not described, and procedures or steps that can be understood by those skilled in the art are not described. did

Throughout the specification, when a part is said to "comprising" or "including" a certain element, it means that it may further include other elements, not excluding other elements, unless otherwise stated. do. In addition, terms such as “… unit”, “… unit”, and “module” described in the specification mean a unit that processes at least one function or operation, which is hardware or software or a combination of hardware and software. can be implemented as Also, “a or an”, “one”, “the” and like terms are used herein in the context of describing various embodiments (particularly in the context of the claims below). Unless otherwise indicated or clearly contradicted by context, both the singular and the plural can be used.

Hereinafter, preferred embodiments according to various embodiments will be described in detail with reference to the accompanying drawings. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The detailed description set forth below in conjunction with the accompanying drawings is intended to describe exemplary embodiments of various embodiments, and is not intended to represent a single embodiment.

In addition, specific terms used in various embodiments are provided to help understanding of various embodiments, and the use of these specific terms may be changed into other forms without departing from the technical spirit of various embodiments. .

Referring to FIG. 1 , a data serving structure setting system according to various embodiments may be implemented in various types of electronic devices. For example, the data serving structure setting system may be implemented in the server device 100 and the device 200 interlocked with the server device 100 . In other words, the server device 100 and the device 200 linked to the server device 100 may perform operations according to various embodiments of the present disclosure based on the data serving structure setting system implemented in each device. can Meanwhile, the data serving structure setting system according to various embodiments is not limited to that shown in FIG. 1 and may be implemented in more various electronic devices and servers.

The server device 100 according to various embodiments may be a device that performs wireless and wired communication with the device 200 interlocked with the server device 100 and includes a storage having a large storage capacity. For example, the server device 100 may be a cloud device connected to the device 200 linked to the server device 100 .

The device 200 linked to the server device 100 according to various embodiments may be a device that can be used by an individual user such as a desktop PC, a tablet PC, or a mobile terminal. In addition, other electronic devices performing similar functions may be used as the device 200 linked to the server device 100 .

A data serving structure setting system according to various embodiments may include various modules for operation. The modules included in the data serving structure setting system are computer codes implemented so that a physical device (eg, the server device 100) in which the data serving structure setting system is implemented (or included in the physical device) can perform a specified operation. or one or more instructions. In other words, the physical device in which the data serving structure setting system is implemented stores a plurality of modules in the memory in the form of computer code, and when the plurality of modules stored in the memory are executed, the plurality of modules correspond to the plurality of modules. to perform specified actions.

Referring to FIG. 2 , a server device 100 and a device 200 linked to the server device 100 may include an input/output unit 210, a communication unit 220, a storage 230, and a processor 240. can

The input/output unit 210 may be various interfaces or connection ports that receive user input or output information to the user. The input/output unit 210 may include an input module and an output module, and the input module receives a user input from a user. User input may be made in various forms including key input, touch input, and voice input. Examples of input modules capable of receiving such user input include a traditional keypad, keyboard, and mouse, as well as a touch sensor that detects a user's touch, a microphone that receives a voice signal, a camera that recognizes gestures through image recognition, A proximity sensor including at least one of an illuminance sensor or an infrared sensor for detecting user approach, a motion sensor for recognizing a user's motion through an acceleration sensor or a gyro sensor, and various other types of sensors that detect or receive user input. There is an input means, and the input module according to the embodiment of the present disclosure may include at least one of the devices listed above. Here, the touch sensor may be implemented as a piezoelectric or capacitive touch sensor that detects a touch through a touch panel attached to a display panel or a touch film, an optical touch sensor that detects a touch by an optical method, and the like. In addition, the input module may be implemented in the form of an input interface (USB port, PS/2 port, etc.) connecting an external input device that receives a user input instead of a device that detects a user input by itself. Also, the output module may output various types of information. The output module may include at least one of a display for outputting an image, a speaker for outputting sound, a haptic device for generating vibration, and other various types of output means. In addition, the output module may be implemented in the form of a port type output interface connecting the above-described individual output means.

For example, an output module in the form of a display may display text, still images, and moving images. Displays include liquid crystal displays (LCDs), light emitting diodes (LEDs) displays, organic light emitting diodes (OLEDs) displays, flat panel displays (FPDs), and transparent displays. display), curved display, flexible display, 3D display, holographic display, projector, and other various types of devices capable of performing image output functions. may contain at least one. Such a display may be in the form of a touch display integrally formed with the touch sensor of the input module.

The communication unit 220 may communicate with other devices. Accordingly, the server device 100 and the device 200 interlocked with the server device 100 may transmit and receive information with other devices through a communication unit. For example, the server device 100 and the device 200 linked to the server device 100 may perform mutual communication using a communication unit or perform communication with other devices.

Here, communication, that is, transmission and reception of data may be performed by wire or wireless. To this end, the communication unit includes a wired communication module that accesses the Internet through a LAN (Local Area Network), a mobile communication module that accesses a mobile communication network through a mobile communication base station to transmit and receive data, and a wireless local area network (WLAN) such as Wi-Fi. Area Network)-based communication method or WPAN (Wireless Personal Area Network)-based communication method such as Bluetooth or Zigbee, a short-distance communication module, or GNSS (Global Navigation Satellite System) such as GPS (Global Positioning System) ), or a combination thereof.

The storage 230 may store various types of information. Storage may temporarily or semi-permanently store data. For example, the storage of the server 100 includes an operating system (OS) for driving the server 100, a program for generating data or braille for hosting a website, or an application (eg, a web application). ) may be stored. In addition, the storage may store the modules in the form of computer code as described above.

Examples of the storage 230 include a hard disk drive (HDD), a solid state drive (SSD), a flash memory, a read-only memory (ROM), a random access memory (RAM), and the like. This can be. Such storage may be provided in a built-in type or a detachable type.

The processor 240 controls overall operations of the server device 100 and the device 200 interlocked with the server device 100 . To this end, the processor 240 may perform calculations and processing of various types of information and control operations of components of the server 100 . For example, the processor 240 may execute a program or application for setting a data serving structure. The processor 240 may be implemented as a computer or a similar device according to hardware, software, or a combination thereof. In terms of hardware, the processor 240 may be implemented in the form of an electronic circuit that performs a control function by processing electrical signals, and in terms of software, it may be implemented in the form of a program that drives the processor 240 in hardware. Meanwhile, in the following description, unless otherwise noted, operations of the server device 100 and the device 200 interlocked with the server device 100 may be interpreted as being performed under the control of the processor 240 . That is, when the modules implemented in the above-described data serving structure setting system are executed, the modules cause the processor 240 to cause the server device 100 and the device 200 linked to the server device 100 to perform the following operations. can be interpreted as controlling.

In summary, various embodiments may be implemented through various means. For example, various embodiments may be implemented by hardware, firmware, software, or a combination thereof.

In the case of hardware implementation, the method according to various embodiments includes one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), and FPGAs. (field programmable gate arrays), processors, controllers, microcontrollers, microprocessors, etc.

In the case of implementation by firmware or software, the method according to various embodiments may be implemented in the form of a module, procedure, or function that performs functions or operations described below. For example, software codes can be stored in memory and run by a processor. The memory may be located inside or outside the processor, and may exchange data with the processor by various means known in the art.

Hereinafter, various embodiments will be described in more detail based on the above technical idea. The above-described contents may be applied to various embodiments described below. For example, operations, functions, and terms that are not defined in various embodiments described below may be performed and described based on the contents described above.

In the following description, various embodiments will be described on the premise that the server device 100 performs a data serving structure setting operation, and according to various embodiments, the server device 100 provides information related to the data serving structure setting operation. can be transmitted and received with the device 200 linked to the server device 100.

According to FIG. 3, the server device 100 may set a data serving structure, and in order to perform an operation of setting the data serving structure, a plurality of customer page domains for services provided by the server device 100. Checking information about the frontend including a plurality of backend data domains related to information about the frontend and a database for services (301), and a data serving structure between the frontend and the backend Setting information for setting is obtained (303), and based on the acquired setting information, a data serving structure including a main data serving structure for serving data requested by the front end may be set (305). In FIG. 3 , the backend associated with the database may be a node that generates information to be provided to the frontend, and data generated at the corresponding node can be effectively provided to the frontend according to a data serving structure according to various embodiments.

According to various embodiments, in operation 301, the server device 100 provides information on a frontend including a plurality of customer page domains for the service and a plurality of backends associated with a database for the service. Information about the backend including the data domain can be checked.

Referring to identification number 401, the front end may include a plurality of customer page domains for services, and the customer page domains are UI/UX (user interface/user interface/user interfaces) of services provided by the server device 100. experience) may mean a domain corresponding to various service pages that a user can access. As an example, the user can use an item search page to search for items on the UI/UX of the service, a category page to classify items, and an item detail page including detailed information of a specific item. and/or My Page including the user's personal information, etc., and the server device 100 corresponds to the customer page domain corresponding to the item search page, the customer page domain corresponding to the category page, and the item A front end including a customer page domain corresponding to the detailed page and/or a customer page domain corresponding to My Page may be identified.

Referring to identification number 401, the front end includes a plurality of customer page domains as described above, and manages data requested from each page and each page domain corresponding to each page according to the user's UI / UX access. It can be understood as a set user-side management stage.

Referring to identification number 403, the backend may include a plurality of backend data domains related to a database for a service, and each data included in a database that the server device 100 stores and manages data. It may refer to a domain that manages the type or kind of data corresponding to the type or type of data determined for . For example, according to the characteristics of the service provided by the server device 100, data for logistics management (Fulfillment), data of a seller selling an item on the service (Seller), and data related to discount information of the item (Promotions/Benefits ) and/or review data (Product Review) written for the item may be generated and stored, and the server device 100 corresponds to the backend data domain corresponding to the data for logistics management and the seller's data. A backend including a backend data domain, a backend data domain corresponding to data related to item discount information, and/or a backend data domain corresponding to review data may be identified.

Referring to identification number 403, the backend includes a plurality of backend data domains as described above, and is a database-side management unit configured to provide or check data stored or managed in relation to the service provided by the server device 100. can be understood as

In this case, a plurality of backend data domains included in the backend may be configured to manage various data managed in the database of 405 according to characteristics of each data domain.

According to various embodiments, in operation 303, the server device 100 may obtain configuration information for configuring a data serving structure between the front end and the back end.

For example, a data serving structure between a front end and a back end may refer to a structure for serving data requested by a user side management unit from a database side management unit according to a user's UI/UX connection. . In particular, in service data management in the case where the service provided by the server device 100 corresponds to e-commerce, various data necessary for the customer page are stored in the front-end customer page domain related to the customer page. It can be based on MSA (Micro Service Architecture), which is served by targeting a corresponding data domain in charge of a certain backend side, and for MSA, high throughput and low latency to handle high input/output traffic are guaranteed. In addition, it is necessary to provide a core logic structure that can secure data consistency, freshness, or system availability.

However, even if the core logical structure is designed, when the characteristics of the data processed in the customer page domain or data domain are different and operate based on different code bases, even if the core logical structure is used, duplicate codes increase and management becomes difficult. may occur. Therefore, it is necessary to prevent the core logical structure from being fragmented according to each customer page domain or data domain. To this end, the data serving structure, which is the target of the setting information acquired by the server device 100 according to operation 303, is different from the customer page domain. It may correspond to a data serving structure configured to prevent fragmentation by having scalability corresponding to a domain or data domain.

That is, the data serving structure, which is the object of the setting information acquired by the server device 100 according to operation 303, has an additional data serving structure that can correspond to various customer page domains or data domains based on the main data serving structure for data serving. Implemented in an additive manner, it can have extensibility for customer page domains or data domains of different characteristics.

For example, the setting information acquired by the server device 100 according to operation 303 is main setting information for setting a main data serving structure corresponding to a basic data serving structure for performing data serving between the front end and the back end. can include For example, when a main data serving structure is established between the front end and the back end based on the main configuration information, data requested by the front end may be served from the back end. Such a main data serving structure may be implemented in the same manner as in FIG. 5 .

The main data serving structure 501 may include various components for data serving. Components for the main data serving structure include a plurality of data queues 503 corresponding to a plurality of backend data domains, A common storage 505 for storing data transmitted through a plurality of data queues, and a common serving layer for calling data requested from the storage and transmitting it to the front end. (Serving Layer) 507 may be included.

In the main data serving structure of 501, various data of a database managed in a plurality of backend data domains may be transmitted to data queues corresponding to respective backend data domains. Here, the data queue may refer to a data queue that receives and stores data provided from the transmitting end, waits until the stored data is transmitted to the receiving end, and then transmits the stored data to the receiving end. there is. In 503, one data queue corresponds to one back-end data domain or one or more back-end data domains, receives data provided from the corresponding back-end data domain, stores it, waits, and stores the stored data according to the data update cycle of the storage. can be transmitted to the storage side. That is, the data queue of 503 can play a role of waiting for data received from the backend data domain side and then delivering the data to the storage side according to the update cycle of the storage side.

Also, in the main data serving structure of 501, the storage may receive and store various data of the database through a plurality of data queues. Storage is data that stores and manages database data identically or similarly so that the serving layer can call the requested data from the front-end only by accessing the storage without accessing the back-end data domain for the convenience of data serving. It can mean storage space. In 505, the storage can receive and store the data of the database managed by the backend data domain. In particular, a data queue exists between the backend data domain and the storage, and the data queue transfers the data of the database from the data domain. Receive and store, and the storage can receive data stored in the data queue at regular intervals. The serving layer may acquire desired data by calling the desired data for the storage storing the data received in this way. That is, the storage of 505 receives the data of the database managed in the backend data domain through a plurality of data queues, stores the data of the database, and plays a role of enabling the serving layer to obtain desired data. .

In the main data serving structure of 501, the serving layer may obtain desired data by accessing the storage. The serving layer may perform a function of calling various data requested from the storage through a plurality of customer page domains included in the front end. In 507, the serving layer may receive a request to call certain data from the customer page corresponding to the front end, access the storage, call and acquire the requested data as a call target, and when desired data is obtained, return it to the front end. can be transmitted to the end side.

For example, the setting information acquired by the server device 100 according to operation 303 is first additional setting information for setting a first additional data serving structure added to the main data serving structure or added to the main data serving structure. and second additional setting information for setting a second additional data serving structure to be configured. For example, 1) When a first additional data serving structure is established between the front end and the back end based on the first additional configuration information, data requested from the front end is transmitted from the back end in a manner different from that of the main data serving structure. 2) When a second additional data serving structure is established between the front end and the back end based on the second additional configuration information, data requested from the front end side is transferred in a manner different from that of the main data serving structure to the back end. 3) This is the same even if both the first additional data serving structure and the second additional data serving structure are configured between the front end and the back end based on the first additional configuration information and the second additional configuration information. can be The first additional data serving structure and the second additional data serving structure may be implemented in the same manner as shown in FIGS. 6 to 8 .

The first supplementary data serving structure 601 may include various components for data serving, and the components for the first supplementary data serving structure obtain at least some data included in data stored in the storage from the storage. For the specific data included in the cache 603, at least some of the data stored in the cache, when the specific data is updated and the updated specific data is confirmed in the storage, the updated specific data An update data queue (Notification Queue) 605 for storing and transmitting to the cache, and a cache update manager (Cache invalidator) 607 that manages to transmit specific updated data to the cache through the update data queue may be included. there is.

In the first additional data serving structure of 601 , the cache may acquire and store some of data stored in the storage from the storage. The cache promotes easy access to data from the serving layer side for reasons such as the data to be called is frequently called from the serving layer side in the process of the serving layer accessing the storage and calling the desired data, or the cache promotes easy access to data from the serving layer side, or stores multiple data for storage. It may refer to a separate data storage space that stores some data stored in the storage so that the serving layer can easily access it in order to prevent a problem that may occur due to latency in the storage. In 603, the cache is located between the storage and the serving layer, and the serving layer can first call desired data from the cache before calling it from the storage and transmit it to the front end. If the serving layer confirms that the desired data is not in the cache because the desired data is not stored in the cache, the serving layer may call the desired data from the storage and transmit it to the front end.

If a cache configured to acquire and store some of the data stored in the storage, such as 603, is located between the storage and the serving layer, when the specific data stored in the cache is updated in the backend data domain, the storage queues the data. However, if the cache does not immediately check whether the specific data is updated, the storage stores the updated specific data, while the cache stores the specific data that has not been updated. There may be problems with storing data. In order to prevent such a problem, it is necessary to check and manage updates of data commonly stored in storage and cache, and the update notification queue of 605 can perform such a role.

When updated data is checked and managed on the backend data domain side for data stored in storage, the updated data is delivered and stored in a data queue related to the data among a plurality of data queues, and then stored in a specific data queue corresponding to the update cycle of the storage. It is transferred to storage according to the cycle. At this time, if the data is data stored in both the storage and cache as described above, when the storage receives the updated data, the cache must receive the same updated data, so the updated data is stored in the storage and updated It should be designed so that it can also be delivered to the notification queue. Based on this design, the update notification queue can hold the updated data, and when the updated data is checked in the storage and update data queue according to the storage update cycle, the cache update manager of 607 updates through the update data queue. You can instruct the cached data to be transferred to the cache.

Since some of the data in the storage that the cache acquires and stores from the storage has a priority purpose of facilitating data call of the serving layer, it can be selected from data stored in the storage in consideration of the priority of data call by the serving layer. . That is, some of the data stored in the cache may be data selected to be stored in the cache based on a data call priority among data stored in the storage, and the priority of such a data call may be determined by the number of data calls from the serving layer. . For example, data to be stored in the cache may be selected in the order of the number of data calls, and data such as an image of an item with a high number of data calls from a customer page, an item name, and a price may be stored in the cache.

At this time, in the first additional data serving structure of 601, the serving layer may access the storage in the background while accessing the cache to call data having a high data call priority. If it is confirmed that updated data is stored in the storage for specific data but not updated data is stored in the cache, update request information for the specific data may be generated and transmitted by the serving layer. .

The second additional data serving structure 701 may include various components for data serving, and in particular, components for serving data requiring real-time update management. In the second supplementary data serving structure, for data that is determined to require real-time update among data stored in the database, real-time updated data is obtained for the corresponding data through a specific data queue related to the corresponding data among a plurality of data queues. A real time cache 703 for storing, and a real time data update manager 705 for managing transmission of real time updated data to the real time cache through the specific data queue may be included.

In the second additional data serving structure of 701, the real-time cache may acquire and store data identified as requiring real-time update management among data stored in the plurality of data queues from the plurality of data queues based on a period close to real time. there is. Among the data stored in the database and managed by the backend data domain, data that is important to reflect real-time updates as updated in real time, such as inventory of items or promotional discount prices, can be checked in advance, and multiple data corresponding to the backend data domain In the data queue of , when data updated in real time for the confirmed data is confirmed, the real-time updated data can be transmitted to the real-time cache.

That is, if any data is identified as requiring management of real-time update, the data queue related to the data can check the data updated in real time in response to the data, and the data queue can display the updated data in real time. sent to the cache. From the point of view of the data queue, the data stored in the data queue is transmitted to the storage according to the update cycle of the storage, but if there is data that needs to be managed for real-time update, the data updated in real time related to that data can be transmitted to the real-time cache at a period close to real-time that is much faster than the storage update period. Therefore, by setting a real-time cache such as 703, it is possible to prevent a problem in which storage or cache cannot store data updated in real time in real time, and a real-time cache manager is set separately, such as 705. It becomes possible to manage the transmission of real-time update data.

When the second additional data serving structure such as 701 is set, the serving layer caches the corresponding data based on whether the desired data corresponds to data requiring real-time updating, if the corresponding data corresponds to data requiring real-time updating. It can be called from and transmitted to the front end.

At this time, in FIG. 7, for convenience, it is shown that a cache, which is a component of the first additional data serving structure, is set in addition to the second additional data serving structure, but this corresponds to a secondary example, and in some cases, the serving layer is directly stored as a storage rather than a cache. You can also access and call the desired data.

8, the first additional data serving structure 801 and the second additional data serving structure 803 are set together, which is based on the fact that both the first additional setting information and the second additional setting information are included in the setting information. it could be The data queue, storage, serving layer, cache, update notification queue, cache update manager, real-time cache, and real-time cache update manager included in FIG. 8 may operate as described above with reference to FIGS. 5 to 7 .

In the case of FIG. 8 , the serving layer calls the corresponding data from both the real-time cache and the cache based on whether the desired data corresponds to the data requiring real-time update, if the corresponding data corresponds to the data requiring real-time update. Information such as the time staff included in the cache and the data called from the cache is checked, and more recent data among the called data is transmitted to the front end. On the other hand, if the corresponding data does not correspond to data that needs to be updated in real time, the serving layer calls the corresponding data from the cache and transmits it to the front-end. sent to the frontend. To this end, the server device 100 may perform an operation of obtaining information on whether data requested by the front end, that is, data desired by the serving layer corresponds to data requiring real-time updating.

Meanwhile, the serving layer may request data from both the cache and the real-time cache regardless of the characteristics of the data as described above. Similarly, when data is called from both the cache and the real-time cache, the serving layer can deliver more recent data to the front end based on information such as a timestamp of the called data.

For example, there may be cases in which specific data requested from the front end is requested from the front end in the form of a data set including a plurality of data including specific data, rather than being requested from the front end in a single data form. can If a data set including a plurality of data is requested from the front end and it is confirmed that specific data included in the plurality of data is requested, all of the plurality of data will be called by the serving layer from the storage, cache, or real-time cache. Only when possible, the specific data can be configured to be transmitted to the front end by the serving layer.

That is, requesting a data set including multiple data from the front end is often to utilize all of the plurality of data in a customer page or a certain area of the customer page, so all data included in the data set is called Data omission can be prevented by transmitting a plurality of data included in a data set to the front end only when possible. For example, when a data set including data such as real-time inventory for an item, item image, item name, and/or item price is requested from an item detail page, the real-time inventory data identified as requiring real-time update is stored in the real-time cache. It will be called and the remaining data will be called from cache or storage. If the item image data is not checked in cache or storage then the real-time inventory data may not be sent to the front end even if it is correctly called from the real-time cache.

In order to manage the data set type request as described above, identification information corresponding to the data set may be determined and set for a plurality of data included in the data set. A plurality of data included in the data set has one identification information corresponding to the data set in common, and based on this identification information, all of the plurality of data included in the data set is called from storage, cache, or real-time cache. A point can be identified, and omission of data can be prevented.

For example, the setting information acquired by the server device 100 in operation 303 may include information for interworking the first additional data serving structure and the second additional data serving structure with the main data serving structure. As described above with reference to FIGS. 5 to 8 , since the first additional data serving structure and the second additional data serving structure correspond to structures serving data in association with the main data serving structure, even if the additional data serving structure is added, seamless data Interworking information for establishing mutual interworking so that serving can be performed may be included in setting information acquired by the server device 100 in operation 303 .

For example, in step 303, the operation of the server device 100 obtaining setting information is performed by providing a first additional data serving structure or a second additional data serving structure according to a backend data domain corresponding to various types of service domains constituting a service. This may include an operation of obtaining setting information including the first additional setting information or the second additional setting information selectively or adaptively so that the structure can be additionally set, and the specific operation may be performed as shown in FIG. 9 . there is.

FIG. 9 is a diagram illustrating an operation method of acquiring setting information by the server device 100 for setting a data serving structure according to various embodiments. FIG. 9 may correspond to an operation method in which an operation of acquiring setting information by the server device 100 in 303 of FIG. 3 is embodied.

Regarding the service provided by the server device 100, the server device 100 verifies information on a specific service domain among various types of service domains forming services such as a product service domain, an order service domain, or a review service domain. In operation 901, information on one or more backend data domains corresponding to the specific service domain among a plurality of backend data domains may be checked (operation 903).

The server device 100 provides first information on whether a first additional data serving structure needs to be set and second information about whether a second additional data serving structure needs to be set, based on the checked information on one or more backend data domains. is checked (905), and then, according to the first information and the second information, first additional setting information for adding the first additional data serving structure or second additional setting information for adding the second additional data serving structure is obtained. Setting information determined to be included may be acquired (907).

Since a backend data domain related to data requested in a specific service domain is highly likely to be a part of all backend data domains, a first additional data serving structure or a second supplementary data serving structure is used to serve data for some related backend data domains. By determining whether or not is necessary, setting information determined to include the first additional setting information or the second additional setting information may be obtained from the server device 100 . Through such an operation of obtaining setting information of the server device 100, a data serving structure may be designed to optimize data serving for some backend data domains corresponding to a specific service domain.

1001 is setting information for a data serving structure, indicating selection options related to settings for a main data serving structure, a first additional data serving structure, and/or a second supplementary data serving structure, and 1003 is information related to each service domain. , information identifying which backend data domain can correspond to each service domain or information related to whether a first additional data serving structure or a second additional data serving structure is required for data serving.

Depending on the information indicated in 1003, a corresponding backend data domain may be determined differently for each service domain as in 1005, and when the corresponding backend data domain is changed in this way, a data serving structure for each service domain may be changed as in 1007. . That is, each service domain can have different data serving structures based on the main data serving structure, the first supplementary data serving structure, and/or the second supplementary data serving structure. For example, in a product domain corresponding to certain backend data domains (Catalog, Seller, Subscribe Order), a first supplementary data serving structure and a second supplementary data serving structure are both added and configured to the main data serving structure. In the review domain corresponding to the other backend data domain (Member), it can be confirmed that only the first additional data serving structure is added to the main data serving structure.

As shown in FIG. 10, by applying different data serving structures according to each service domain or backend data domain corresponding to each service domain, the server device 100 configures each service domain or backend data domain corresponding to each service domain. It is possible to have scalability for data serving for each service domain, and the effectiveness of data serving can be increased by applying an optimal data serving structure for each service domain or a backend data domain corresponding to each service domain.

According to various embodiments, in operation 305, the server device 100 may configure a data serving structure including a main data serving structure for serving data requested by the front end based on the acquired setting information.

For example, the data serving structure set by the server device 100 according to operation 305 basically includes the main data serving structure, and the first additional setting information or second setting information included in the setting information obtained in operation 303 described above. A first additional data serving structure or a second additional data serving structure may be further included according to the additional configuration information.

For example, in operation 305, the data requested from the front end to be served may be data requested from a first customer page corresponding to a first customer page domain included in a plurality of customer page domains included in the front end. can

For example, the data serving structure set by the server device 100 according to operation 305 is a circuit for preventing incorrect data from being served from the failed component when a failure occurs in each component included in the data serving structure. It may include application information about circuit breakers. For example, when a failure occurs in the real-time cache storing real-time updated data in the second supplementary data serving structure including the real-time cache, the serving layer serves data containing errors from the failed real-time cache and provides the data to the user. Rather, it may be more appropriate in terms of customer experience to provide the user with previous data that is not updated in real time. Therefore, the server device 100 can isolate the failed real-time cache by blocking an access path to prevent the serving layer from accessing the real-time cache based on the circuit breaker. In this case, the serving layer is not updated from the cache or storage in real time. However, error-free data can be served.

In addition, in addition to the application of the circuit breaker as described above, if a situation arises in which real-time updated data must be served due to the importance or necessity of data even though a failure occurs in the real-time cache, the server device 100 provides a real-time It is also possible to directly access a plurality of data queues storing the correct data updated in real time without going through the cache, and call and serve the correct data updated in real time.

For example, the data serving structure set by the server device 100 according to operation 305 may correspond to one data serving structure among a plurality of data serving structures existing between the front end and the back end. In other words, a plurality of data serving structures set by the server device 100 according to operation 305 may exist between the front end and the back end as shown in FIG. 11, and each data serving structure serves data independently of each other, thereby affecting each other. may not give The server device 100 sets up a plurality of independent data serving structures and corresponds each data serving structure to different customer page domains, so that even if a problem occurs in the data serving structure for a specific customer page domain, other customers Page domains can be designed to serve data correctly.

Two data serving structures corresponding to 1101 and 1103 are set between the front end and the back end of FIG. 11, and the data serving structure corresponding to 1101 serves data for some customer page domains among a plurality of customer page domains. and the data serving structure corresponding to 1103 is used to serve data for the rest of the customer page domain. By setting a plurality of data serving structures as shown in FIG. 11, even if a problem occurs in one data serving structure and data serving for one customer page domain becomes impossible, data serving for another customer page domain is performed by another data serving structure. this could be possible

In particular, among a plurality of customer page domains, there may be some customer page domains with high importance for user experience, such as a customer page domain for an item search page and a customer page domain for an item detail page. For the customer page domain, a data serving structure of 1101 may be set as a Critical Serving Path (CSP). Conversely, for the rest of the customer page domains that are not of high importance in relation to user experience, such as customer page domains for item category pages and customer page domains for my pages related to user information, the data serving structure of 1103 as non-CSP (N-CSP) can be set.

The server device 100 sets the data serving structure 1101 for CSP and the data serving structure 1103 for N-CSP in parallel and independently, so that a problem occurs in the data serving structure for the customer page domain that is not important. However, the data serving structure for other customer page domains with high importance can still be designed to be utilized for data serving. In addition, when a problem occurs in the data serving structure of 1101 for a customer page domain with a high importance, the server device 100 provides a customer page domain with a high importance to supplement data serving for a customer page domain with a high importance. It can also be designed to serve data by utilizing the data serving structure of 1103.

Each information generated or provided by the server device 100 performing the setting operation of the data serving structure based on FIGS. 3 to 11 according to the above-described embodiments is combined in various forms in relation to the setting of the data serving structure. It is self-evident that it can be created or provided.

Embodiments of the present invention disclosed in this specification and drawings are only presented as specific examples to easily explain the technical content of the present invention and help understanding of the present invention, and are not intended to limit the scope of the present invention. That is, it is obvious to those skilled in the art that other modified examples based on the technical idea of the present invention can be implemented. In addition, each of the above embodiments can be operated in combination with each other as needed. For example, all embodiments of the present invention may be implemented by a system in which parts are combined with each other.

In addition, the method according to the system according to the present invention may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer readable medium.

As such, various embodiments of the present invention may be implemented as computer readable codes in a computer readable recording medium from a specific point of view. A computer readable recording medium is any data storage device capable of storing data readable by a computer system. Examples of computer readable recording media include read only memory (ROM), random access memory (RAM), and compact disk-read only memory (CD-ROM). ), magnetic tapes, floppy disks, optical data storage devices, and carrier waves (such as data transmission over the Internet). The computer readable recording medium may also be distributed across networked computer systems, so that computer readable code is stored and executed in a distributed manner. In addition, functional programs, code, and code segments for achieving various embodiments of the present invention can be easily interpreted by programmers skilled in the field to which the present invention is applied.

It will also be appreciated that the apparatus and method according to various embodiments of the present invention can be realized in the form of hardware, software, or a combination of hardware and software. Such software may include, for example, volatile or non-volatile storage devices, such as RAM, memory chips, devices or integrated circuits, whether erasable or rewritable. Or, for example, a compact disk (CD), DVD, magnetic disk or magnetic tape, such as optically or magnetically recordable and at the same time machine (eg, computer) readable storage medium may be stored. . Methods according to various embodiments of the present invention may be implemented by a computer including a control unit and a memory, or a vehicle including such a memory or computer, and the memory may include a program including instructions for implementing the embodiments of the present invention. or an example of a machine-readable storage medium suitable for storing programs.

Accordingly, the present invention includes a program including code for implementing the device or method described in the claims of this specification and a storage medium readable by a machine (such as a computer) storing such a program. In addition, such a program may be transmitted electronically through any medium, such as a communication signal transmitted through a wired or wireless connection, and the present invention appropriately includes equivalents thereto.

Although the above has been described with reference to the embodiments of the present invention, the embodiments of the present invention disclosed in this specification and drawings are only presented as specific examples to easily explain the technical content of the present invention and help understanding of the present invention. It is not intended to limit the scope of In addition, the embodiments according to the present invention described above are merely illustrative, and those skilled in the art will understand that various modifications and embodiments of equivalent scope are possible therefrom. Therefore, the true technical protection scope of the present invention should be defined by the following claims.

Claims

A method for setting a data serving structure by an electronic device providing a service,

Checking information on a frontend including a plurality of customer page domains for the service and information on a backend including a plurality of backend data domains related to a database for the service;

obtaining setting information for setting a data serving structure between the front end and the back end; and

Based on the setting information, setting the data serving structure including a main data serving structure for serving data requested by the front end,

How to set up a data serving structure.
According to claim 1,

The setting information includes main setting information for setting the main data serving structure;

The main data serving structure,

a plurality of data queues corresponding to the plurality of backend data domains; Storage for storing data transmitted through the plurality of data queues; And a serving layer that calls the requested data from the storage and transmits it to the front-end.

How to set up a data serving structure.
According to claim 2,

The setting information,

First additional setting information for setting a first additional data serving structure added to the main data serving structure; or

Further comprising second additional setting information for setting a second additional data serving structure added to the main data serving structure,

How to set up a data serving structure.
According to claim 3,

The first additional data serving structure,

a cache acquiring and storing at least some data included in the data stored in the storage from the storage; an update data queue configured to transmit the updated first data to the cache when updated first data corresponding to the first data included in the at least some data is identified in the storage; and a cache update manager managing to transmit the updated first data to the cache through the update data queue;

The second additional data serving structure,

Second data corresponding to the second data through a specific data queue related to the second data among the plurality of data queues, with respect to second data determined to require real-time update among data stored in the database. Real time cache for acquiring and storing (Real time Cache); and a real-time cache update manager managing to transmit the real-time updated second data to the real-time cache through the specific data queue.

How to set up a data serving structure.
According to claim 4,

The setting information,

The first additional data serving structure and the second additional data serving structure include information for interworking with the main data serving structure.

How to set up a data serving structure.
According to claim 4,

The updated first data is transmitted to the storage through a data queue related to the first data among the plurality of data queues based on a first cycle corresponding to an update cycle of the storage when the first data is updated. it has been,

Instructing the cache update manager to transmit the updated first data to the cache through the update data queue when the updated first data is identified in the storage and the update data queue according to the first cycle ,

How to set up a data serving structure.
According to claim 4,

The step of setting the data serving structure,

Based on the first additional setting information, setting the data serving structure including the main data serving structure and the first additional data serving structure;

The serving layer preferentially calls the requested data from the cache and transmits it to the front end;

When the requested data is not confirmed in the cache, the serving layer calls the requested data from the storage and transmits it to the front end.

How to set up a data serving structure.
According to claim 4,

The at least some data stored in the cache is selected to be stored in the cache based on a data call priority among data stored in the storage;

The data call priority is determined based on the number of data calls from the serving layer.

How to set up a data serving structure.
According to claim 4,

When the updated first data is identified in the storage and the first data that is not updated in the cache is identified, update request information for the first data is transmitted by the serving layer,

How to set up a data serving structure.
According to claim 4,

The real-time updated second data is transmitted to the real-time cache through the specific data queue based on a second period corresponding to real time when the second data is updated.

How to set up a data serving structure.
According to claim 4,

The step of setting the data serving structure,

Based on the second additional setting information, setting the data serving structure including the main data serving structure and the second additional data serving structure;

Based on whether the requested data corresponds to data requiring real-time updating, the serving layer calls the requested data from the real-time cache and transmits it to the front-end.

How to set up a data serving structure.
According to claim 4,

The step of setting the data serving structure,

Setting the data serving structure to include the main data serving structure, the first additional data serving structure, and the second additional data serving structure based on the first additional setting information and the second additional setting information. include,

If the requested data corresponds to data requiring real-time updating, the serving layer calls the requested data from both the cache and the real-time cache;

In the cache and the real-time cache, the latest data among the data called by the serving layer is transmitted to the front end.

How to set up a data serving structure.
According to claim 12,

When the requested data does not correspond to data requiring real-time update, the serving layer calls the requested data from the cache and transmits it to the front end.

How to set up a data serving structure.
According to claim 12,

The method,

Further comprising obtaining information on whether the requested data corresponds to data requiring real-time update,

How to set up a data serving structure.
According to claim 12,

When the front end requests a data set including a plurality of data and the requested data is included in the plurality of data,

The requested data is transmitted to the front end based on the fact that all of the plurality of data are called by the serving layer in the storage, the cache, or the real-time cache.

How to set up a data serving structure.
According to claim 15,

Identification information corresponding to the data set is set for the plurality of data,

Based on the identification information, it is confirmed that all of the plurality of data are called from the storage, the cache, or the real-time cache.

How to set up a data serving structure.
According to claim 4,

The step of obtaining the setting information is,

checking information about a first service domain related to the service;

checking information on one or more backend data domains related to the first service domain among the plurality of backend data domains;

checking first information on whether or not the first additional data serving structure needs to be set and second information about whether or not the second additional data serving structure needs to be set, based on the information on the one or more backend data; and

Acquiring the setting information determined to include the first additional setting information or the second additional setting information based on the first information and the second information,

How to set up a data serving structure.
According to claim 1,

The requested data is requested from a first customer page corresponding to a first customer page domain included in the plurality of customer page domains,

How to set up a data serving structure.
In an electronic device for setting a data serving structure related to a service,

processor; and

comprising one or more memories for storing one or more instructions;

The one or more instructions, when executed, cause the processor to:

Checking information on a frontend including a plurality of customer page domains for the service and information on a backend including a plurality of backend data domains related to a database for the service;

obtaining setting information for setting a data serving structure between the front end and the back end; and

Controlling the processor to perform the step of setting the data serving structure including the main data serving structure for serving data requested by the front end based on the setting information;

electronic device.