TWI864521B - Operating method for configuring data serving structure and electronic apparatus supporting thereof - Google Patents

Abstract

Disclosed is a method of configuring a data serving structure by an electronic apparatus providing a service, the method including 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, obtaining configuration information for configuring a data serving structure between the frontend and the backend, and based on the configuration information, configuring the data serving structure including a main data serving structure for serving data requested by the frontend.

Description

Operation method for constructing data service structure and electronic equipment supporting the operation method

The present invention relates to a method and an apparatus for constructing a data service structure, and more particularly, the present invention relates to a method and an electronic apparatus for constructing a data service structure based on a service structure of a selectable application for data service.

With the development of electronic technology, e-commerce has become a shopping field. Customers can purchase items online without having to go to a shopping mall or market in person, and the items purchased online are delivered to the delivery address requested by the customer.

In the context of e-commerce, since providing 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 documents in related fields, such as KR101756594B1 or KR101500849B1.

[Technical objectives]

One aspect provides an electronic device for constructing a data service structure based on a service structure with selectable applications.

The technical objectives to be achieved by the present invention are not limited to the technical aspects mentioned above, and those familiar with the technology to which the present invention belongs will clearly understand other technical aspects not mentioned from the following description. [Technical Solution]

Various example embodiments may provide a method of operating an electronic device for constructing a data service structure and an electronic device supporting the method.

According to one aspect, a method for constructing a data service structure by providing a service through an electronic device is provided, the method comprising: identifying information about a front end including a plurality of client page domains used for the service and information about a back end including a plurality of back end data domains associated with a database used for the service; obtaining architecture information for constructing a data service structure between the front end and the back end; and based on the architecture information, constructing the data service structure to include a master data service structure for serving data requested by the front end.

In one embodiment, the architecture information may include main architecture information for constructing the main data service structure, and the main data service structure includes a plurality of data queues corresponding to the plurality of backend data domains, a storage device storing data transmitted through the plurality of data queues, and a service layer that calls the request data from the storage device and transmits the request data to the front end.

In one aspect, the architecture information may further include first additional architecture information for architecture a first additional data service structure to be added to the main data service structure or second additional architecture information for architecture a second additional data service structure to be added to the main data service structure.

In one embodiment, the first additional data service structure may include: a cache area, which is configured to obtain and store at least a portion of the data contained in the data stored in the storage; an update data queue, which is configured to transmit the updated first data to the cache area when the updated first data corresponding to the first data contained in the at least a portion of the data is identified in the storage; and a cache update manager, which is configured to manage the updated first data transmitted to the cache area through the update data queue. The second additional data service structure may include: a real-time cache area, which is constructed to obtain and store real-time updated second data corresponding to the second data through a specific data queue related to the second data among the multiple data queues, and the second data is determined to require real-time update in the data stored in the database; and a real-time cache update manager, which is constructed to manage the real-time updated second data transmitted to the real-time cache area through the specific data queue.

In one aspect, the architecture information may include information for enabling the first additional data service structure and the second additional data service structure to interact with the main data service structure.

In one aspect, when the first data is updated, based on a first cycle corresponding to an update cycle of the memory, the updated first data can be transmitted to the memory through a data queue related to the first data among the plurality of data queues, and when the updated first data is identified in the memory and the update data queue according to the first cycle, the cache update manager can be instructed to transmit the updated first data to the cache area through the update data queue.

In one embodiment, constructing the data service structure may include constructing the data service structure including the main data service structure and the first additional data service structure based on the first additional architecture information. The service layer may preferentially call the request data from the cache and transmit the request data to the front end. When the request data is not recognized in the cache, the service layer may call the request data from the memory and transmit the request data to the front end.

In one aspect, the at least a portion of the data stored in the cache may be selected to be stored in the cache based on a data call priority among the data stored in the memory, and the data call priority may be determined based on the number of data calls from the service layer.

In one aspect, when the updated first data is identified in the memory and the unupdated first data is identified in the cache, an update request message for the first data may be transmitted by the service layer.

In one aspect, when the second data is updated, the real-time updated second data may be transmitted to the real-time cache through the specific data queue based on a second cycle corresponding to the real-time.

In one embodiment, constructing the data service structure may include constructing the data service structure including the main data service structure and the second additional data service structure based on the second additional architecture information. Based on whether the request data corresponds to data that needs to be updated in real time, the service layer may call the request data from the real-time cache and transmit it to the front end.

In one embodiment, constructing the data service structure may include constructing the data service structure including the main data service structure, the first additional data service structure, and the second additional data service structure based on the first additional architecture information and the second additional architecture information. When the request data corresponds to data that needs to be updated in real time, the service layer may call the request data from both the cache area and the real-time cache area. The latest data of the data called by the service layer from the cache area and the real-time cache area may be transmitted to the front end.

In one aspect, when the request data does not correspond to data that needs to be updated in real time, the service layer can call the request data from the cache and transmit it to the front end.

In one aspect, the method may further include obtaining information about whether the requested data corresponds to data that needs to be updated in real time.

In one aspect, when the front-end request includes a data set of a plurality of data and the request data is included in the plurality of data, the request data may be transmitted to the front-end based on all of the plurality of data being called by the service layer in the storage, the cache, or the real-time cache.

In one aspect, identification information corresponding to the data set is constructed for the plurality of data, and the identification information can be used to identify all of the plurality of data to be called from the memory, the cache, or the immediate cache.

In one embodiment, obtaining the architecture information may include: identifying information about a first service domain associated with the service; identifying information about one or more backend data domains among the plurality of backend data domains that are associated with the first service domain; based on the information about the one or more backend data domains, identifying first information about whether the first additional data service structure will be constructed and second information about whether the second additional data service structure will be constructed; and based on the first information and the second information, obtaining the architecture information determined to include the first additional architecture information or the second additional architecture information.

In one aspect, the request data may be from a first customer page request corresponding to a first customer page domain included in the plurality of customer page domains.

According to another aspect, an electronic device for constructing a data service structure associated with a service is also provided, the electronic device including a processor and one or more memories storing one or more instructions, wherein the one or more instructions, when executed, control the processor to execute: identifying information about a front end including a plurality of client page domains for the service and information about a back end including a plurality of back end data domains associated with a database for the service; obtaining architectural information for constructing a data service structure between the front end and the back end; and based on the architectural information, constructing the data service structure including a master data service structure for serving data requested by the front end.

The above-mentioned various exemplary embodiments of the present invention are only some exemplary embodiments of the present invention, and those skilled in the art can obtain and understand various exemplary embodiments reflecting the technical features of various exemplary embodiments of the present invention based on the detailed description to be described below. [Effect]

The present invention provides a method for constructing a data service structure based on a service structure of an electronic device that can be selectively applied to construct a data service structure, so that it has a technical effect in reducing the processing delay used for data services and optimizing data services.

The effects that can be obtained in the present invention are not limited to the effects mentioned above, and those skilled in the art to which the present invention belongs will clearly understand other effects that are not mentioned from the following description.

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

In the description of the drawings, processes or operations that would make the subject matter of various exemplary embodiments unclear are not described, and processes or operations that can be understood by a person of ordinary skill in the art are not described.

Throughout the specification, when a component is referred to as "including or comprising" a specific component, unless otherwise specified, it means that other components may be further included, rather than excluding other components. In addition, terms such as "...component", "...group" and "module" described in the specification mean a unit that processes at least one function or operation, which can be implemented as hardware or software or a combination of hardware and software. In addition, "a", "an", "the" and similar related terms may be used in the context of describing various example embodiments (especially in the context of the following patent application scope) to include both the singular and the plural, unless otherwise indicated or clearly contradictory to the context.

In the following, some example embodiments will be described in detail with reference to the accompanying drawings. The detailed description below in conjunction with the accompanying drawings is intended to describe exemplary embodiments of various example embodiments, but is not intended to represent the only embodiment.

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

FIG. 1 is a diagram illustrating a data service structure architecture system for implementing a method of operating an electronic device for constructing a data service structure according to various example embodiments.

Referring to FIG. 1 , a data service structure architecture system according to various example embodiments can be implemented in various types of electronic devices. For example, the data service structure architecture system can be implemented in a server device 100 and a device 200 that interacts with the server device 100. In other words, the server device 100 and the device 200 that interacts with the server device 100 can perform operations according to various example embodiments of the present invention based on the data service structure architecture system implemented in each device. At the same time, the data service structure architecture system according to various example embodiments is not limited to the system shown in FIG. 1 , but can be implemented in more various electronic devices and servers.

The server device 100 according to various example embodiments may be a device that performs wireless and wired communications with the device 200 interacting 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 interacting with the server device 100.

The device 200 interacting with the server device 100 according to various exemplary embodiments may be a device that can be used by a human user, such as a desktop personal computer (PC), a tablet PC, or a mobile terminal and the like. In addition, other electronic devices performing similar functions may be used as the device 200 interacting with the server device 100.

According to various example embodiments, a data service structure architecture system may include various modules for operation. The modules included in the data service structure architecture system may be computer codes or one or more instructions implemented so that a physical device (e.g., server device 100) in which the data service structure architecture system is implemented (or included in the physical device) can execute a specified operation. In other words, the physical device in which the data service structure architecture system is implemented can store a plurality of modules in the form of computer codes in the memory, and when executing the plurality of modules stored in the memory, the plurality of modules can cause the physical device to execute the specified operations corresponding to the plurality of modules.

FIG. 2 is a diagram illustrating an architecture of a server device and a device interacting with the server device according to various example embodiments.

2 , the server device 100 and the device 200 interacting with the server device 100 may each include an input/output component 210 , a communication component 220 , a storage 230 , and a processor 240 .

The input/output component 210 may be a variety of interfaces or ports for receiving user input or outputting information to the user. The input/output component 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 performed in various forms, including a key input, a touch input, and a voice input. Examples of input modules that can receive this user input may include a traditional keypad or keyboard, a mouse, and a touch sensor that detects a user's touch, a microphone that receives a voice signal, a camera that recognizes a gesture and the like through image recognition, a proximity sensor that includes at least one of an illumination sensor or an infrared sensor that detects a user's approach, a motion sensor that recognizes a user's movement through an accelerometer or a gyroscope sensor, and other various types of input components that sense or receive various types of user input, and an input module according to an example embodiment of the present invention may include at least one of the above-listed devices. Here, the touch sensor may be implemented as a piezoelectric or capacitive touch sensor for detecting a touch through a touch panel or a touch film attached to a display panel, an optical touch sensor for detecting a touch by an optical method, and the like. In addition, the input module may be implemented in the form of an input interface (universal serial bus (USB) port, personal system 2 (PS/2) port, etc.) for connecting to an external input device that receives a user input rather than a device that detects a user input itself. In addition, the output module may output various information. The output module may include at least one of a display that outputs an image, a speaker that outputs a sound, a tactile device that generates vibration, and other various types of output components. In addition, the output module can be implemented in the form of a one-port output interface to connect the above-mentioned individual output components.

For example, the display output module can display text, static images and dynamic images. The display can include a liquid crystal display (LCD), a light emitting diode (LED) display, an organic light emitting diode (OLED) display, a flat panel display (FPD) and a transparent display, a curved display, a flexible display, a three-dimensional (3D) display, a holographic display, a projector and at least one of other types of devices capable of performing an image output function. Such a display can be in the form of a touch display integrally formed with the touch sensor of the input module.

The communication component 220 can communicate with other devices. Therefore, the server device 100 and the device 200 interacting with the server device 100 can transmit information to/receive information from other devices through the communication component. For example, the server device 100 and the device 200 interacting with the server device 100 can use a communication component to communicate with each other or with other devices.

Here, communication (i.e., transmission and reception of data) may be performed wired or wirelessly. For this purpose, the communication means may consist of a wired communication module accessing the Internet and the like via a local area network (LAN), a mobile communication module accessing a mobile communication network via a mobile communication base station and transmitting and receiving data, a short-range communication module using a wireless local area network (WLAN) communication method such as Wireless Fidelity (Wi-Fi) or a wireless personal area network (WPAN) communication method such as Bluetooth or Zigbee, a satellite communication module using a global navigation satellite system (GNSS) such as a global positioning system (GPS), or a combination thereof.

The memory 230 can store various types of information. The memory can temporarily or semi-permanently store data. For example, an operating program (operating system: OS) for driving the server 100, data for hosting a website, or data about a program or application (e.g., web application) for generating Braille, and the like can be stored in the memory of the server 100. In addition, the memory can store modules in the form of the above-mentioned computer code.

Examples of the memory 230 may 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 memory may be provided as a built-in type or a removable type.

The processor 240 controls the overall operation of the server device 100 and the devices 200 that interact with the server device 100. To this end, the processor 240 can perform calculations and processing of various types of information and can control the operation of components of the server 100. For example, the processor 240 can execute a program or application for building a data service structure. The processor 240 can be implemented as a computer or a similar device based on hardware, software, or a combination thereof. In hardware, the processor 240 can be implemented in the form of an electronic circuit that processes electrical signals to perform a control function, and in software, it can be implemented in the form of a program that drives the processor 240 in the hardware. Meanwhile, in the following description, unless otherwise stated, the operations of the server device 100 and the device 200 interacting with the server device 100 may be interpreted as being executed under the control of the processor 240. That is, when executing the module implemented in the above-mentioned data service structure architecture system, the module may be interpreted as the processor 240 controlling the server device 100 and the device 200 interacting with the server device 100 to perform the following operations.

In summary, various example embodiments can be implemented by various components. For example, various example embodiments can be implemented by hardware, firmware, software or a combination thereof.

In terms of hardware implementation, the methods according to various exemplary embodiments may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), a processor, a controller, a microcontroller, a microprocessor, and the like.

In terms of implementation by firmware or software, the methods according to various exemplary embodiments may be implemented in the form of a module, a program or a function that performs the following functions or operations. For example, the software code may be stored in a memory and driven by a processor. The memory may be located inside or outside the processor, and data may be exchanged with the processor through various known components.

In the following, various exemplary embodiments will be described in more detail based on the above technical ideas. The above content can be applied to the various exemplary embodiments described below. For example, operations, functions, terms and the like not defined in the various exemplary embodiments described below can be performed and described based on the above content.

In the following description, various exemplary embodiments will be described under the premise that the server device 100 executes a data service architecture operation, and according to various exemplary embodiments, the server device 100 can transmit/receive information related to a data service architecture operation with the device 200 interacting with the server device 100.

FIG. 3 is a flow chart illustrating an operation method of the server device 100 for constructing a data service structure according to various exemplary embodiments.

3 , the server device 100 can construct a data service structure. To perform an operation of constructing the data service structure, the server device 100 can identify information about a front end including a plurality of client page domains of a service provided by the server device 100 and information about a back end including a plurality of back end data domains associated with a database for a service in operation 301, obtain architecture information for constructing a data service structure between the front end and the back end in operation 303, and construct a data service structure including a master data service structure for serving data requested by the front end based on the obtained architecture information in operation 305. In FIG. 3 , according to various example embodiments, the database-related backend may be a node that generates information provided to the front end, and the data generated at the corresponding node may be effectively provided to the front end according to the data service structure.

According to various example embodiments, in operation 301, the server device 100 may identify information about a front end including a plurality of client page domains for a service and information about a back end including a plurality of back end data domains associated with a database for a service.

FIG. 4 is a diagram illustrating an overview of a data flow associated with a front-end and a back-end data service associated with a service.

Referring to element symbol 401, the front end may include a plurality of client page domains for a service, and the client page domain may refer to a domain corresponding to various service pages that a user can access on the user interface/user experience (UI/UX) of a service provided by the server device 100. For example, a user may access an item search page for searching for an item on the UI/UX of the service, a category page for categorizing items, an item detail page containing detailed information about a particular item, and/or a my page containing the user's personal information, and the like, and in response, the server device 100 may identify a front end that includes a customer page domain corresponding to an item search page, a customer page domain corresponding to a category page, a customer page domain corresponding to an item detail page, and/or a customer page domain corresponding to my page, and the like.

Referring to component symbol 401, the front end includes the above-mentioned multiple client page domains, so that it can be understood as a user-side management component that is structured to manage each page and the data requested from each page domain corresponding to each page according to the user's UI/UX access.

Referring to element symbol 403, the backend may include a plurality of backend data domains associated with a database for a service, and the backend data domain may refer to a domain in which the server device 100 manages a corresponding type or category of data in response to a type or category of data determined for each data contained in a database for storing and managing data. For example, based on the characteristics of the service provided by the server device 100, data for logistics management (fulfillment), data of a seller who sells an item in the service (seller), data related to discount information about the item (promotion/benefits) and/or review data written for the item (product review) and the like may be created and stored, and in response, the server device 100 may identify a backend that includes a backend data domain corresponding to data for logistics management, a backend data domain corresponding to data of a seller, a backend data domain corresponding to data related to discount information about an item and/or a backend data domain corresponding to review data.

Referring to component symbol 403, the backend includes the aforementioned plurality of backend data domains, so that it can be understood as a database-side management component that is structured to provide or identify data stored or managed by a service provided by the server device 100.

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

According to various example embodiments, in operation 303, the server device 100 may obtain architecture information about a data service architecture between an architecture front end and a back end.

For example, the data service structure between the front-end and the back-end may refer to a structure and the like for serving data requested from a database-side management component by connecting a user-side management component according to a user's UI/UX. Specifically, in the case where the service provided by the server device 100 corresponds to data management of the service in e-commerce, it may be based on a microservice architecture (MSA), in which various data required for the customer page are served by targeting a specific back-end-side responsible data domain corresponding to a front-end-side customer page domain related to the customer page, and for MSA, a core logic structure needs to be provided that can ensure high throughput and low latency to handle high input/output traffic, and ensure data consistency, freshness, or system availability.

However, even if the core logic structure is designed, the characteristics of the data processed in the client page domain or the data domain are different and when operating based on different code bases, even if the core logic structure is utilized, a problem may occur in which duplicate code may increase and management becomes difficult. Therefore, it is necessary to prevent the core logic structure from being fragmented according to each client page domain or data domain, and for this purpose, the data service structure (which is the target of the architecture information obtained by the server device 100 according to operation 303) corresponds to the data service structure that is architected to prevent fragmentation by having scalability corresponding to different client page domains or data domains.

That is, based on the main data service structure for data services, the data service structure (which is the target of the architecture information obtained by the server device 100 according to operation 303) can be implemented in a manner that allows additional data service structures corresponding to various client page domains or data domains to be added, so that it can have scalability for different characteristics of client page domains or data domains.

For example, the architecture information obtained by the server device 100 according to operation 303 may include main architecture information for constructing a main data service structure, and the main data service structure corresponds to a basic data service structure for executing a data service between the front end and the back end. For example, when the main data service structure is constructed between the front end and the back end based on the main architecture information, the data requested by the front end side can be provided from the back end side. This main data service structure can be implemented in the same manner as FIG. 5.

FIG. 5 is a diagram illustrating a state in which a master data service structure is constructed between a front end and a back end.

A master data service structure 501 may include various components for data services, and the components used for the master data service structure may 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 service layer 507 that calls data requested by the front end from the storage and transmits it to the front end.

In the main data service structure 501, various data of a database managed in a plurality of back-end data domains can be transmitted to a data queue corresponding to each back-end data domain. Here, the data queue can refer to a data queue line that performs the functions of receiving and storing data provided from a transmission component, waiting until the stored data is transmitted to a receiving component, and transmitting the stored data to the receiving component. In the plurality of data queues 503, a data queue corresponds to a back-end data domain or one or more back-end data domains, can receive data provided from the corresponding back-end data domain and store it and then queue it, and can send data stored according to the data update cycle of the memory to the memory side. That is, the data queue 503 can queue the data received from the back-end data domain side and deliver the data to the memory side according to the update cycle of the memory side.

In addition, in the main data service structure 501, the storage can receive and store various data of the database through multiple data queues. The storage can refer to a data storage space that stores and manages the data in the database in the same or similar manner, so that the service layer can call the request data from the front end by accessing the storage without accessing the back-end data domain to facilitate data services. In the common storage 505, the storage can receive and store data from a database managed by a back-end data domain, and specifically, there is a data queue between the back-end data domain and the storage, and the data queue receives and stores data from the database of the data domain, and the storage can receive data stored in the data queue according to a specific cycle. The service layer can obtain the required data by calling the required data to the storage for storing the received data in this way. That is, the common storage 505 can receive data from a database managed in a back-end data domain through a plurality of data queues, store the data of the database, and enable the service layer to obtain the required data.

In the main data service structure 501, the service layer can access the storage and obtain the required data by calling the required data. The service layer can perform a function of calling various data requested through multiple client page domains included in the front end from the storage. In the common service layer 507, the service layer can call specific data from the client page corresponding to the front end upon request, can access the storage and obtain the data requested as the call target by calling the data, and can transmit it back to the front end side when the required data is obtained.

For example, the architecture information obtained by the server device 100 according to operation 303 may include first additional architecture information for architecture of a first additional data service structure added to the main data service structure or second additional architecture information for architecture of a second additional data service structure added to the main data service structure. For example, 1) when a first additional data service structure is constructed between the front end and the back end based on the first additional architecture information, data requested from the front end side is provided from the back end in a manner different from the main data service structure, 2) when a second additional data service structure is constructed between the front end and the back end based on the second additional architecture information, data requested from the front end side is provided from the back end in a manner different from the main data service structure, 3) when both the first additional data service structure and the second additional data service structure are constructed between the front end and the back end based on the first additional architecture information and the second additional architecture information, this may also be the same. Such a first additional data service structure and a second additional data service structure may be implemented in the same manner as in FIGS. 6 to 8.

FIG. 6 is a diagram illustrating a state in which a first additional data service structure is added and constructed between a front end and a back end.

A first additional data service structure 601 may include various components for data service. As an element for the first additional data service structure, the first additional data service structure 601 may include: a cache 603, which obtains and stores at least some of the data stored in the storage relative to the specific data contained in at least some of the data stored in the cache when the specific data is updated and the update specific data is confirmed in the storage; an update data queue (notification queue) 605, which is used to store the update specific data and send it to the cache; and a cache update manager (cache invalidator) 607, which manages sending the update specific data to the cache through the update data queue.

In the first additional data service structure 601, the cache area can obtain and store some data stored in the memory from the memory. In the process of the service layer accessing the memory and calling the required data, the cache area can mean a separate data storage space used to store some data stored in the memory, so that the service layer can easily access the memory to promote easy data access on the service layer side due to reasons such as frequent calls from the service layer side of the data as the call target or prevent a problem of memory delay caused by calling a large amount of data into the memory. The cache 603 is located between the storage and the service layer, and the service layer can transfer the requested data to the front end by first calling the requested data from the cache before calling the requested data from the storage. If the service layer confirms that the requested data is not in the cache (because the requested data is not stored in the cache), the service layer can call the requested data from the storage and transfer it to the front end.

Like cache 603, if a cache that is structured to obtain and store some data stored in a memory is located between the memory and the service layer, when specific data stored in the cache is updated on the back-end data domain side, the memory can obtain and store the updated specific data in response to the specific data through the data queue, but if the cache does not immediately verify whether the specific data is updated, a problem may occur in which the memory stores the updated specific data while the cache stores the unupdated specific data. To prevent this problem, it is necessary to check and manage the updates of the data stored in the memory and the cache together, and the update notification queue 605 can play this role.

When update data is identified and managed for data stored in a memory on the back-end data domain side, the update data is delivered and stored in a data queue associated with the corresponding data among a plurality of data queues and then transmitted to the memory according to a specific cycle corresponding to the update cycle of the memory. At this time, if the data is stored in both the memory and the cache as described above, when the memory receives the update data, the cache must also receive the update data in the same manner and therefore it should be designed so that the update data can be delivered to the update notification queue when it is stored in the memory. Based on this design, the update notification queue can maintain update data, and when data updated according to the update cycle of the memory is identified in the memory and the update data queue, the cache update manager 607 can be instructed to send the update data to the cache area through the update data queue.

Some data in the cache area obtained from the storage and stored in the storage has the main purpose of promoting the data call of the service layer, so it can be selected by the service layer from the data stored in the storage based on the data call priority. That is, some data stored in the cache area can be selected based on a data call priority among the data stored in the storage, and the priority of this data call can be determined by the number of data calls from the service layer. For example, data stored in the cache may be selected in order of the number of data calls, and data with a large number of data calls from a customer page (such as an item image, item name, price, and the like) may be stored in the cache.

At this time, in the first additional data service structure 601, the service layer can access the storage in the background and access the cache to call data with a high data call priority. If it is confirmed that the update data is stored in the storage but the update data is not stored in the cache for the specific data, the update request information corresponding to the specific data can be generated and transmitted by the service layer.

FIG. 7 is a diagram illustrating a state in which a second additional data service structure is added and constructed between the front end and the back end.

A second additional data service structure 701 may include various components for data services, and in particular, may include components for serving data that requires real-time update management. In the second additional data service structure, for data stored in the database that is determined to require real-time update, it may include: a real-time cache area 703, which obtains and stores real-time update data for the corresponding data through a specific data queue associated with the corresponding data among a plurality of data queues; and a real-time cache update manager (real-time data updater) 705, which manages the transmission of real-time update data to the real-time cache area through the specific data queue.

In the second additional data service structure 701, the real-time cache area can obtain and store data stored in the plurality of data queues based on a near-real-time cycle to identify data that needs to be updated and managed in real time. Among the data stored in the database and managed by the back-end data domain, important data to be updated in real time (such as reflecting the real-time updated inventory or promotional discount prices) can be pre-identified, and in the plurality of data queues corresponding to the back-end data domain, when real-time update data is identified for the identified data, the real-time update data can be transmitted to the real-time cache area.

That is, if any data is identified as data that needs to be updated and managed in real time, the data queue associated with the corresponding data can respond to the corresponding data and identify the updated data in real time, and the data queue transmits the updated data in real time to the real-time cache area. From the perspective of a data queue, the data held by the data queue is transmitted to the memory according to the update cycle of the memory, but if there is data that is identified as data that needs to be updated and managed in real time, the real-time update data associated with the corresponding data can be transmitted to the real-time cache area according to a cycle that is much faster than the update cycle of the memory. Therefore, by constructing a real-time cache area such as the real-time cache area 703, the problem that the memory or cache area cannot store the real-time update data in real time can be prevented. Additionally, like the real-time cache manager 705, a real-time cache manager is independently constructed to manage the transfer of real-time update data from the data queue to the real-time cache area.

Therefore, when constructing the second additional data service structure 701, if the corresponding data corresponds to data that needs to be updated in real time, the service layer can call the corresponding data from the real-time cache and transmit it to the front end based on whether the required data corresponds to data that needs to be updated in real time.

At this time, FIG. 7 shows that for convenience, in addition to the second additional data service structure, a cache area is also constructed as a component of the first additional data service structure, but this is an auxiliary example, and in some cases, the service layer can call the required data by directly accessing the storage instead of the cache area.

FIG. 8 is a diagram showing a state in which a first additional data service structure and a second additional data service structure are added and constructed between a front end and a back end.

In Figure 8, a first additional data service structure 801 and a second additional data service structure 803 are constructed together, and it can be based on the following points: the architecture information includes both the first additional architecture information and the second additional architecture information. The data queue, storage, service layer, cache area, update notification queue, cache update manager, real-time cache area and real-time cache update manager included in Figure 8 can be operated as described above with reference to Figures 5 to 7.

With respect to FIG. 8 , if the corresponding data corresponds to data that needs to be updated in real time, the service layer calls the corresponding data from both the real-time cache and the cache based on whether the desired data corresponds to data that needs to be updated in real time, and transmits the latest data in the called data to the front end by identifying the real-time cache and information such as a time scale and the like contained in the data called from the cache. On the other hand, if the corresponding data does not correspond to data that needs to be updated in real time, the service layer calls the corresponding data from the cache and transmits it to the front end, and if the corresponding data cannot be called from the cache, it accesses the register, calls the corresponding data, and transmits it to the front end. To this end, the server device 100 may perform an operation of obtaining information about whether the data requested by the front end (ie, the data expected by the service layer) corresponds to data that needs to be updated in real time.

At the same time, the service layer can make a data request to both the cache and the real-time cache, regardless of the characteristics of the data described above. Similarly, when calling data from both the cache and the real-time cache, the service layer can deliver more recent data to the front end based on information such as a timestamp of the called data and the like.

For example, there may be a situation 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 the specific data) rather than in the form of a single data. If the front end requests a data set including a plurality of data and it is confirmed that specific data included in the plurality of data is requested, the specific data may be architected to be transmitted from the service layer to the front end only when all the plurality of data can be called from storage, cache, or real-time cache by the service layer.

That is, since in many cases a data set containing multiple data is requested from the front end in order to utilize all multiple data in a client page or a specific area of a client page, data omission can be prevented by allowing multiple data contained in the data set to be transmitted to the front end only when all data contained in the data set can be called. For example, when a data set including data such as real-time inventory of an item, an item image, an item name and/or an item price is requested from an item detail page, the real-time inventory data identified as needing real-time update will be called from the real-time cache and the remaining data will be called from the cache or storage, and if the item image data is not verified by the cache or storage, then even if the real-time inventory data is correctly called from the real-time cache, it cannot be transmitted to the front end.

In order to manage the above data set type request, identification information corresponding to the data set can be determined and constructed for the plurality of data included in the data set. The plurality of data included in a data set has a common piece of identification information corresponding to the data set, and based on the identification information, all the plurality of data included in the data set can be confirmed to be called from the storage, cache or immediate cache, and data omission can be prevented.

For example, the architecture information obtained by the server device 100 in operation 303 may include information for making the first additional data service structure and the second additional data service structure interact with the main data service structure. As described above with reference to Figures 5 to 8, the first additional data service structure and the second additional data service structure correspond to structures that provide data that interact with the main data service structure, so even if an additional data service structure is added, interaction information for the architectures to interact with each other so that the data service can be successfully executed may be included in the architecture information obtained by the server device 100 in operation 303.

For example, in operation 303, the operation of the server device 100 obtaining the architecture information may include an operation of obtaining the architecture information, wherein the first additional architecture information or the second additional architecture information is selectively or adaptively included so that the first additional data service structure or the second additional data service structure can be additionally structured according to the back-end data domain corresponding to the service domain of various types of service formed. The operation may be performed as described in detail with reference to FIG. 9.

FIG9 is a diagram showing an operation method in which a server device 100 for constructing a data service structure obtains structure information according to various exemplary embodiments. FIG9 may correspond to a detailed operation method in which the server device 100 obtains structure information in operation 303 of FIG3.

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

In operation 905, the server device 100 may identify first information about whether a first additional data service structure is to be constructed and second information about whether a second additional data service structure is to be constructed based on identification information about one or more backend data domains. In operation 907, the server device 100 may obtain architecture information determined to include first additional architecture information for adding a first additional data service structure or second additional architecture information for adding a second additional data service structure based on the first information and the second information.

Since the backend data domain associated with the data requested in a specific service domain is likely to be a part of the entire backend data domain, by determining whether some of the related backend data domains need the first additional data service structure or the second additional data service structure for data service, the architecture information determined to include the first additional architecture information or the second additional architecture information can be obtained from the server device 100. Through this architecture information acquisition operation of the server device 100, a data service structure can be designed to optimize the data service of some backend data domains corresponding to a specific service domain.

FIG. 10 is a diagram illustrating an example of constructing a data service structure based on a backend data domain corresponding to a service domain.

Component symbol 1001 indicates architecture information for a data service structure, and indicates a selection option related to the architecture for a main data service structure, a first additional data service structure and/or a second additional data service structure, and component symbol 1003 indicates information related to each service domain, which may include information confirming which back-end data domains can match each service domain or information related to whether the data service requires a first additional data service structure or a second additional data service structure, and the like.

According to the information indicated by element symbol 1003, a corresponding backend data domain may be determined differently for each service domain indicated by element symbol 1005, and as described above, when the corresponding backend data domain changes, the data service structure of each service domain may be changed as indicated by 1007. That is, each service domain may have a different data service structure based on the main data service structure, the first additional data service structure and/or the second additional data service structure. As an example, in a product domain corresponding to a specific backend data domain (catalog, seller, subscription order), it can be confirmed that both the first additional data service structure and the second additional data service structure have been added to the main data service structure and have been structured, and in a review domain corresponding to a different backend data domain (member), it can be confirmed that only the first additional data service structure has been added and structured to the main data service structure and has been structured.

As shown in FIG. 10 , by enabling different data service structures to be applied according to each service domain or a back-end data domain corresponding to each service domain, the server device 100 can have scalability of data services for each service domain or a back-end data domain corresponding to each service domain, and by applying an optimal data service structure for each service domain or a back-end data domain corresponding to each service domain, the effectiveness of the data service can be improved.

According to various example embodiments, in operation 305, the server device 100 may construct a data service structure including a master data service structure for serving data requested by the front end based on the obtained architecture information.

For example, the data service structure constructed by the server device 100 according to operation 305 may basically include the main data service structure, and may additionally include a first additional data service structure or a second additional data service structure based on the first additional schema information or the second additional schema information included in the schema information obtained in the above operation 303.

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

For example, when components included in the data service structure fail, the data service structure constructed by the server device 100 in operation 305 may include application information for a circuit breaker to prevent incorrect data from being served from a failed component. For example, when a failure occurs in a real-time cache storing real-time updated data in a second additional data service structure including a real-time cache, the customer experience of providing users with previous data that is not updated in real time may be more appropriate than if the service layer serves erroneous data from the failed real-time cache and provides it to the user. Therefore, the server device 100 can isolate the failed real-time cache by blocking the access path based on the circuit breaker to prevent the service layer from accessing the real-time cache, and in this case, the service layer can serve data from the cache or storage that is not updated in real time but has no errors.

In addition to applying the above-mentioned circuit breaker, when a situation occurs in which even if the real-time cache area fails, it is necessary to serve the real-time updated data due to the importance or necessity of the data, the server device 100 can be structured so that the service layer directly accesses multiple data queues storing the correct data of the real-time update without passing through a real-time cache area in which a failure occurs, and calls and serves the correct data of the real-time update.

For example, the data service structure constructed by the server device 100 according to operation 305 may correspond to one of the plurality of data service structures existing between the front end and the back end. In other words, as shown in FIG. 11 , the plurality of data service structures constructed by the server device 100 according to operation 305 may exist between the front end and the back end, and each data service structure may not affect each other by serving data independently of each other. By constructing a plurality of independent data service structures in this manner and making each data service structure correspond to a different client page domain, the server device 100 may be designed to correctly serve data for another client page domain, even if a problem occurs in the data service structure for a specific client page domain.

FIG. 11 is a diagram illustrating a state in which a plurality of data service structures are constructed between a front end and a back end.

Two data service structures corresponding to component symbols 1101 and 1103 are constructed between the front end and the back end of FIG. 11, and the data service structure corresponding to component symbol 1101 is used to serve data for some of the plurality of customer page domains, and the data service structure corresponding to component symbol 1103 is used to serve data for other customer page domains. By constructing the plurality of data service structures shown in FIG. 11, even if the data service for a specific customer page domain becomes infeasible due to a problem of one data service structure, it is feasible to serve data for a different customer page domain by another data service structure.

Specifically, among the plurality of customer page domains, there may be some customer page domains that are highly important to the customer experience, such as a customer page domain for an item search page and a customer page domain for an item detail page and the like, and a data service structure of component symbol 1101 may be constructed as a key service path (CSP) of some customer page domains with high importance as described above. Conversely, the data service structure of component symbol 1103 may be constructed as a non-CSP (N-CSP) of the remaining customer page domains that are not very important to the user experience, such as a customer page domain for an item category page and a customer page domain for a my page related to user information.

The server device 100 constructs the data service structure of the component symbol 1101 for CSP and the data service structure of the component symbol 1103 for N-CSP in parallel and independently, so that the data service structure for other customer page domains with high importance can still be designed for data service, that is, a problem occurs in the data service structure for non-critical customer page domains. In addition, when a problem occurs in the data service structure of the component symbol 1101 for the customer page domain with high importance, the server device 100 can be designed so that the customer page domain with high importance can serve data by using the data service structure of the component symbol 1103 to supplement the data service for the customer page domain with high importance.

According to the above-mentioned example implementation, it is obvious that the information generated or provided by the server device 100 in combination with the architecture of the data service structure to execute an operation based on the data service structure of Figures 3 to 11 can be combined in various forms.

The example embodiments of the present invention disclosed in this specification and drawings are only provided for specific examples to easily explain the technical content of the present invention and help understand the present invention, and are not intended to limit the scope of the present invention. That is, those skilled in the art to which the present invention belongs will understand that other modified examples can be implemented based on the technical spirit of the present invention. In addition, each of the above-mentioned example embodiments can be combined with each other as needed. For example, all example embodiments of the present invention can be implemented by a system in which components are combined with each other.

In addition, the system or the method similar thereto according to the present invention may be implemented in the form of program instructions, which may be executed through various computer components and recorded in a computer-readable medium.

Thus, in a particular aspect, various exemplary embodiments of the present invention may be embodied as computer readable code on a computer readable recording medium. A computer readable recording medium is any data storage device capable of storing data that can be read by a computer system. Examples of computer readable recording media may include read-only memory (ROM), random access memory (RAM) and compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, optical data storage device and carrier wave (such as data transmission through the Internet and the like). The computer readable recording medium can also be distributed on a computer system connected to a network so that the computer readable code is stored and executed in a distributed manner. In addition, the functional programs, codes and code segments used to achieve various examples of the present invention can be easily interpreted by programmers familiar with the application field of the present invention.

In addition, it should be understood that the apparatus and methods according to various example embodiments of the present invention can be implemented in the form of hardware, software, or a combination of hardware and software. The software can be stored in a volatile or non-volatile storage device, such as a storage device (such as (for example) ROM, whether erasable or rewritable) or a memory (such as (for example) RAM, a memory chip, device or integrated circuit) or a storage medium that can be written optically or magnetically and read by a machine (such as a computer), such as a compact disc (CD), DVD, disk or tape and the like. Methods according to various example embodiments of the present invention may be implemented by a computer comprising a controller and a memory or a vehicle comprising such a memory or a computer. It should be understood that such a memory is an example of a machine-readable storage medium suitable for storing one or more programs comprising instructions for implementing example embodiments of the present invention.

Therefore, the present invention includes a program (including a code for implementing the apparatus or method described in the scope of the patent application of this specification) and a machine (computer and the like) readable storage medium storing this program. In addition, this program can be transmitted electronically through any medium, such as a communication signal transmitted through a wired or wireless connection, and the present invention appropriately includes its equivalent.

Although the above has been described with reference to the example embodiments of the present invention, the example embodiments of the present invention disclosed in this specification and the drawings are only presented as specific examples to easily explain the technical content of the present invention and help understand the present invention, and they are not intended to limit the scope of the present invention. In addition, the above example embodiments according to the present invention are only exemplary, and those skilled in the art will understand that various modifications and equivalent scopes of the embodiments are feasible. Therefore, the scope of the present invention should be defined by the following application scope.

100: Server device 200: Device 210: Input/output component 220: Communication component 230: Storage 240: Processor 301: Operation 303: Operation 305: Operation 401: Customer page domain 403: Backend data domain 405: Data domain 501: Main data service structure 503: Data queue 505: Shared storage 507: Shared service layer 601: First additional data service structure 603: Cache area 605: Update data queue/update notification queue 607: Cache update manager 701: Second additional data service structure 703: Real-time cache area 705: Real-time cache update manager 801: First additional data service structure 803: Second additional data service structure 901: Operation 903: Operation 905: Operation 907: Operation 1001: Architecture information and selection options 1003: Information related to each service domain 1005: Service domain 1007: Change the data service structure of each service domain 1101: Data service structure 1103: Data service structure

FIG. 1 is a diagram illustrating a data service structure architecture system for implementing a method of operating an electronic device for constructing a data service structure according to various example embodiments.

FIG. 2 is a diagram illustrating an architecture of a server device and a device interacting with the server device according to various example embodiments.

FIG. 3 is a flow chart illustrating an operation method of a server device 100 for constructing a data service structure according to various exemplary embodiments.

FIG. 4 is a diagram illustrating an overview of a data flow associated with a front-end and a back-end data service associated with a service.

FIG. 5 is a diagram illustrating a state in which a master data service structure is constructed between a front end and a back end.

FIG. 6 is a diagram illustrating a state in which a first additional data service structure is added and constructed between a front end and a back end.

FIG. 7 is a diagram illustrating a state in which a second additional data service structure is added and constructed between the front end and the back end.

FIG. 8 is a diagram illustrating a state in which a first additional data service structure and a second additional data service structure are added and constructed between a front end and a back end.

FIG. 9 is a flow chart showing an operation method in which a server device 100 for constructing a data service structure obtains structure information according to various example embodiments.

FIG. 10 is a diagram illustrating an example of constructing a data service structure based on a backend data domain corresponding to a service domain.

FIG. 11 is a diagram illustrating a state in which a plurality of data service structures are constructed between a front end and a back end.

301: Operation

303: Operation

305: Operation

Claims (19)

A method for constructing a data service structure by providing a service through an electronic device, the method comprising: identifying information about a front end including a plurality of client page domains for the service and information about a back end including a plurality of back end data domains associated with a database for the service; obtaining architecture information for constructing a data service structure between the front end and the back end; based on the architecture information, constructing the data service structure to include a master data service structure for serving data requested by the front end; receiving a specific request in a client page of the service from a user device of a user using the service; and providing the specific data served by the data service structure to the user in response to the specific request. Device, wherein the data service structure is one of a plurality of data service structures constructed between the front end and the back end, wherein the plurality of data service structures include a data service structure constructed to correspond to some of the plurality of customer page domains with high importance, and another data service structure constructed to correspond to the remaining customer page domains with low importance other than the some of the customer page domains with high importance, and when a problem occurs in the data service structure corresponding to the customer page domain with high importance, the customer page domain with high importance can use the another data service structure to serve data to supplement the data service for the customer page domain with high importance. The method of claim 1, wherein the architecture information includes master architecture information for constructing the master data service structure, and the master data service structure includes: a plurality of data queues corresponding to the plurality of backend data domains; a storage device in which data transmitted through the plurality of data queues is stored; and a service layer, which calls the data requested by the front end from the storage device and transmits the data requested by the front end to the front end. The method of claim 2, wherein the architecture information further comprises: first additional architecture information, which is used to architecture a first additional data service structure added to the main data service structure; or second additional architecture information, which is used to architecture a second additional data service structure added to the main data service structure. The method of claim 3, wherein the first additional data service structure includes: a cache area, which is structured to obtain and store at least a portion of the data contained in the data stored in the memory; an update data queue, which is structured to transmit the updated first data to the cache area when the updated first data corresponding to the first data contained in the at least a portion of the data is identified in the memory; and a cache update manager, which is structured to manage the transmission of the updated first data to the cache through the update data queue. The updated first data of the access zone, and the second additional data service structure includes: a real-time cache zone, which is structured to obtain and store real-time updated second data corresponding to the second data through a specific data queue related to the second data in the plurality of data queues, and the second data is determined to need real-time update in the data stored in the database; and a real-time cache update manager, which is structured to manage the real-time updated second data transmitted to the real-time cache zone through the specific data queue. The method of claim 4, wherein the architecture information includes information for enabling the first additional data service structure and the second additional data service structure to interact with the main data service structure. The method of claim 4, wherein when the first data is updated, based on a first cycle corresponding to an update cycle of the memory, the updated first data is transmitted to the memory through a data queue related to the first data in the plurality of data queues, and when the updated first data is identified in the memory and the update data queue according to the first cycle, the cache update manager is instructed to transmit the updated first data to the cache area through the update data queue. The method of claim 4, wherein constructing the data service structure includes constructing the data service structure including the main data service structure and the first additional data service structure based on the first additional architecture information, the service layer preferentially calls the request data from the cache area and transmits the request data to the front end, and when the request data is not recognized in the cache area, the service layer calls the request data from the memory and transmits the request data to the front end. The method of claim 4, wherein at least a portion of the data stored in the cache is selected to be stored in the cache based on a data call priority among the data stored in the memory, and the data call priority is determined based on the number of data calls from the service layer. The method of claim 4, wherein when the updated first data is identified in the memory and the unupdated first data is identified in the cache, update request information for the first data is transmitted by the service layer. As in the method of claim 4, when the second data is updated, the real-time updated second data is transmitted to the real-time cache area through the specific data queue based on a second cycle corresponding to the real-time. As in the method of claim 4, constructing the data service structure includes constructing the data service structure including the main data service structure and the second additional data service structure based on the second additional architecture information, and based on whether the request data corresponds to data that needs to be updated in real time, the service layer calls the request data from the real-time cache area and transmits the request data to the front end. As in the method of claim 4, constructing the data service structure includes constructing the data service structure including the main data service structure, the first additional data service structure and the second additional data service structure based on the first additional architecture information and the second additional architecture information, when the request data corresponds to data that needs to be updated in real time, the service layer calls the request data from both the cache area and the real-time cache area, and transmits the latest data in the data called by the service layer in the cache area and the real-time cache area to the front end. The method of claim 12, wherein if the request data does not correspond to data that needs to be updated in real time, the service layer calls the request data from the cache area and transmits the request data to the front end. The method of claim 12 further includes: obtaining information about whether the requested data corresponds to data that needs to be updated in real time. The method of claim 12, wherein when the front-end requests a data set including a plurality of data and the request data is included in the plurality of data, the request data is transmitted to the front-end based on all the plurality of data being called by the service layer in the storage, the cache or the real-time cache. The method of claim 15, wherein the plurality of data structures correspond to identification information of the data set, and the identification information is used to identify all of the plurality of data being called from the memory, the cache area, or the real-time cache area. The method of claim 4, wherein obtaining the architecture information includes: identifying information about a first service domain associated with the service; identifying information about one or more backend data domains associated with the first service domain among the plurality of backend data domains; based on the information about the one or more backend data domains, identifying first information about whether the first additional data service structure will be constructed and second information about whether the second additional data service structure will be constructed; and obtaining the architecture information determined to include the first additional architecture information or the second additional architecture information based on the first information and the second information. A method as in claim 1, wherein the request data is from a first customer page request corresponding to a first customer page domain included in the plurality of customer page domains. An electronic device for constructing a data service structure associated with a service, the electronic device comprising: a processor; and one or more memories storing one or more instructions, wherein the one or more instructions, when executed, control the processor to execute: identifying information about a front end containing a plurality of client page domains for the service and about a plurality of back ends containing a database associated with the service; The invention relates to a method for constructing a data service structure between the front end and the back end by obtaining information of a back end of a data domain of the front end; obtaining architecture information for constructing a data service structure between the front end and the back end; constructing the data service structure including a master data service structure for serving data requested by the front end based on the architecture information; receiving a specific request in a client page of the service from a user device of a user using the service; and responding to the specific request, The specific data served by the data service structure is provided to the user device, wherein the data service structure is one of a plurality of data service structures constructed between the front end and the back end, wherein the plurality of data service structures include a data service structure constructed to correspond to some of the plurality of customer page domains with high importance, and another data service structure constructed to correspond to the remaining customer page domains with low importance other than the some of the customer page domains with high importance among the plurality of customer page domains, and when a problem occurs in the data service structure corresponding to the customer page domain with high importance, the customer page domain with high importance can serve data by utilizing the other data service structure to supplement the data service for the customer page domain with high importance.