TW202324093A - 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 of structuring a data service structure and apparatus therefor, and more particularly, the present invention relates to a method of structuring a data service structure based on a service structure for an optional application of data services and its electronic equipment.

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

As far as electronic commerce is concerned, since providing detailed and accurate information about products has an important impact on service satisfaction, various methods for providing more detailed and accurate information are being discussed.

In this regard, reference can be made to documents in the related art, such as KR101756594B1 or KR101500849B1.

[Technical target]

An aspect provides an electronic device for constructing a data service structure based on an optional application service structure.

The technical goals to be achieved by the present invention are not limited to the technical aspects mentioned above, and those skilled in the art to which the present invention pertains 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 building a data service structure and an electronic device supporting the method.

According to an aspect, there is provided a method of structuring a data service structure for providing a service by an electronic device, the method comprising: identifying information about a front end including a plurality of client page domains for the service and about including information about a backend of a plurality of backend data domains related to a database for the service; obtaining architecture information for architecture of a data service structure between the frontend and the backend; and based on the architecture information , Schema The data service structure contains a master data service structure for serving data requested by the front end.

In one aspect, the schema information may include master schema information for structuring 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, which are stored through A storage for the data transmitted by the plurality of data queues, calling the request data from the storage and transmitting the request data to a service layer of the front end.

In one aspect, the schema information may further include first additional schema information for schema-a first additional data service structure added to the master data service structure or for schema-a second additional data service structure added to the master data service structure The second additional structure information of the data service structure.

In one aspect, the first additional data service structure may include: a cache structured to obtain and store from the storage at least a portion of the data contained in the data stored in the storage; a an update data queue structured to transfer the updated first data to the cache area when the updated first data corresponding to the first data included in the at least a portion of the data is identified in the memory; and a a cache update manager structured 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 structured to obtain and store information corresponding to the second data through a specific data queue related to the second data among the plurality of data queues real-time update second data, the second data is determined to require real-time update among the data stored in the database; and a real-time cache update manager, which is structured to manage transmission through the specific data queue to the The real-time updated second data in the real-time cache area.

In one aspect, the schema information may include information for interaction between the first additional data service structure and the second additional data service structure and the master 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, a data queue related to the first data among the plurality of data queues can be used transmitting the updated first data to the storage, and instructing the cache update manager to pass the updated data when the updated first data is identified in the storage and the updated data queue according to the first cycle The queue transmits the updated first data to the cache area.

In one aspect, structuring the data service structure may include structuring the data service structure including the main data service structure and the first additional data service structure based on the first additional structure information. The service layer can preferentially call the request data from the cache area and transmit the request data to the front end. When the request data is not identified in the cache area, the service layer can recall the request data from the storage 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 for storage in the cache based on a data call priority among the data stored in the memory, and may be based on The number of data calls from the service layer is used to determine the priority of the data call.

In one aspect, update request information for the first data may be transmitted by the service layer when the updated first data is identified in the storage and the first data is not updated in the cache area.

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

In one aspect, structuring the data service structure may include structuring the data service structure including the master data service structure and the second additional data service structure based on the second additional structure information. Based on whether the requested data corresponds to data requiring real-time updates, the service layer can call the requested data from the real-time cache and transmit it to the front end.

In one aspect, structuring the data service structure may include structuring the data service structure based on the first additional schema information and the second additional schema information including the master data service structure, the first additional data service structure, and the second 2. Additional data service structure. When the requested data corresponds to data that needs to be updated in real time, the service layer can invoke the requested data from both the cache area and the real-time cache area. The most recent of the data called by the service layer from the cache and the real-time cache may be transmitted to the front end.

In one aspect, when the requested data does not correspond to the data that needs to be updated immediately, the service layer can call the requested data from the cache area 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 requests a data set including a plurality of data and the requested data is included in the plurality of data, the service layer may store the data in the storage, the cache based on all the plurality of data area or the instant cache area to transfer the request data to the front end.

In one aspect, identification information corresponding to the data set is framed for the plurality of data, and the identification information can be used to identify all of the plurality of data from the storage, the cache, or the real-time cache transfer.

In one aspect, obtaining the architecture information may include: identifying information about a first service domain related to the service; identifying information about one or more of the plurality of backend data domains related to the first service domain information about 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 is to be constructed and whether the second additional data service structure is to be constructed and based on the first information and the second information, obtaining the framework information that is determined to include the first additional framework information or the second additional framework information.

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

According to another aspect, there is also provided an electronic device for building a data service structure related to a service, the electronic device includes a processor and one or more memories storing one or more instructions therein, wherein the One or more instructions, when executed, control the processor to: identify information about a front end comprising a plurality of client page domains for the service and information about a rear end comprising a plurality of databases associated with the service information about a backend of the end data domain; obtaining architecture information for structuring a data service structure between the front end and the backend; and based on the architecture information, structuring the data service structure includes a One of the master data service structures of the data.

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

The present invention provides a method for building a data service structure based on a service structure that can be selectively applied to an electronic device for building a data service structure, so that it reduces processing delays for data services and optimizes data services. has a technical effect.

Effects obtainable in the present invention are not limited to the above-mentioned effects, and those skilled in the art to which the present invention pertains will clearly understand other effects 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 explicitly stated otherwise. Each component or feature may be implemented in one form not in combination with other components or features. In addition, various example embodiments may be structured 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, procedures or operations that would make the gist of various example embodiments unclear, and procedures or operations that can be understood by those of ordinary skill are not described.

Throughout the specification, when a component is said to "comprise or comprise" a specific component, unless otherwise specified, it means that other components may be further included, not excluded. 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. Additionally, "a," "an," "the," and similar related terms may be used in the context of describing various example embodiments, particularly in the context of the claims below, to connote both the singular and the plural, Unless otherwise indicated or clearly contradicted by context.

Hereinafter, some example embodiments will be described in detail with reference to the accompanying drawings. The detailed description, set forth below in connection with the accompanying drawings, is intended to describe illustrative embodiments of various example embodiments and is not intended to represent the only embodiments.

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

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

Referring to FIG. 1 , a data service architecture architecture system according to various example embodiments may be implemented in various types of electronic devices. For example, the data service architecture system can be implemented in a server device 100 and a device 200 interacting with the server device 100 . In other words, the server device 100 and the device 200 interacting with the server device 100 can perform operations according to various example embodiments of the present invention based on the data service architecture system implemented in each device. Meanwhile, the data service 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 an apparatus that performs wireless and wired communication of the device 200 interacting with the server device 100 and includes a memory with 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 example embodiments may be a device usable 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 .

A data service architecture architecture system according to various example embodiments may include various modules for operation. A module included in a data service architecture system may be computer code implemented such that a physical device (such as a server device 100) in which the data service architecture system is implemented (or contained in a physical device) can perform a specified operation or one or more directives. In other words, the physical device in which the data service architecture system is implemented can store 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 can cause the entity The device performs specified operations corresponding to a plurality of modules.

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

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

The input/output unit 210 can be various interfaces or connection ports for receiving user input or outputting 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 can be performed in various forms, including a key input, a touch input and a voice input. Examples of input modules that can receive such user input may include a conventional keypad or keyboard, mouse and touch sensors to detect a user's touch, a microphone to receive a voice signal, a Recognize a camera to recognize a gesture and the like, a proximity sensor including at least one of an illumination sensor that detects a user's approach or an infrared sensor, through an acceleration sensor or A gyro sensor to recognize a user's motion, a motion sensor and other various types of input components to sense or receive various types of user input, and an input module according to an example embodiment of the present invention At least one of the above-listed devices may be included. Here, the touch sensor can be implemented as a piezoelectric or capacitive touch sensor for detecting a touch through a touch panel or a touch film attached to the display panel, for An optical touch sensor and the like that detect a touch by an optical method. In addition, the input module can 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 receiving a user input instead of itself A device that detects a user input. In addition, the output module can 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 haptic device that generates vibration, and other various types of output components. In addition, the output module can be implemented in the form of a port-type output interface for connecting the above-mentioned individual output components.

For example, the display output module can display text, still images and dynamic images. The display may 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 , at least one of a three-dimensional (3D) display, a holographic display, a projector, and other various types of devices capable of performing an image output function. Such a display may be in the form of a touch display integrated with the touch sensor of the input module.

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

Here, communication (ie, transmission and reception of data) can be performed by wire or wirelessly. For this purpose, the communication part may be composed of a wired communication module for accessing the Internet and the like through a local area network (LAN), accessing a mobile communication network through a mobile communication base station and transmitting and receiving A mobile communication module for data, short-range communication using a wireless 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 module, a satellite communication module using Global Navigation Satellite System (GNSS) such as Global Positioning System (GPS), or a combination thereof.

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

Examples of storage 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 storage can be provided as a built-in or a removable.

The processor 240 controls the overall operations of the server device 100 and the devices 200 interacting with the server device 100 . To this end, the processor 240 may perform calculations and processing of various types of information and may control operations of components of the server 100 . For example, processor 240 may execute a program or application program for building a data service structure. The processor 240 may be implemented as a computer or a similar device according to a combination of hardware, software, or the like. 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 specified, the operations of the server device 100 and the device 200 interacting 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-mentioned data service architecture system are executed, the modules can be interpreted as the processor 240 controlling the server device 100 and the devices 200 interacting with the server device 100 to perform the following operations.

In sum, various example embodiments may be implemented by various components. For example, various example embodiments may be implemented by any combination of hardware, firmware, software, or the like.

To the extent implemented by hardware, methods according to various example 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 ( PLD), Field Programmable Gate Array (FPGA), a processor, a controller, a microcontroller, a microprocessor, and the like.

As far as being implemented by firmware or software, the methods according to various example embodiments may be implemented in the form of a module, program or function that performs the functions or operations described below. For example, software code may be stored in a memory and driven by a processor. Memory can be located inside or outside the processor, and data can be exchanged with the processor by various known components.

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

In the following description, various example embodiments will be described on the premise that the server device 100 performs a data service structure operation, and according to various example embodiments, the server device 100 can communicate with the device 200 interacting with the server device 100 /Receives information related to the operation of a data service framework.

FIG. 3 is a flowchart illustrating an operation method of the server device 100 for building a data service structure according to various example embodiments.

According to FIG. 3 , the server device 100 can construct a data service structure. In order to perform an operation of the framework data service structure, the server device 100 may identify information about a front end including a plurality of client page domains including a service provided by the server device 100 and information about including and using a service in operation 301 The backend information of a plurality of backend data domains related to a database is obtained in operation 303 to be used to construct the architecture information of a data service structure between the frontend and the backend, and in operation 305 based on the obtained The schema information for structuring a data service structure includes a master data service structure for serving data requested by the front end. In FIG. 3 , according to various example embodiments, the database-related backend may be a node that generates information provided to the frontend, and the data generated at the corresponding node may be efficiently provided to the frontend 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 comprising a plurality of client page domains for a service and information about a front end comprising a plurality of domains associated with a database for a service The backend information of one of the backend data domains.

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

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

Referring to reference numeral 401, the front end includes the above-mentioned plurality of client page domains, so that it can be understood as one of the structures structured to manage each page and request data from each page domain corresponding to each page according to the user's UI/UX access User-side management components.

Referring to reference numeral 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 the data domains in which the server device 100 responds to data contained in storing and managing data. Each data in a database determines a type or category of data and manages a field of data of a corresponding type or type. For example, according to the characteristics of the service provided by the server device 100, it is possible to create and store data for logistics management (fulfillment), data of a seller who sells an item in the service (seller), and information related to discount information about the item. data (promotions/benefits) and/or review data (product reviews) written for items and the like, and in response, the server device 100 can identify backends that contain information corresponding to data for logistics management A backend data field, a backend data field corresponding to a seller's data, a backend data field corresponding to data related to discount information about an item, and/or a backend data field corresponding to review data .

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

In this case, the plurality of backend data domains included in the backend can be structured to manage various data managed by the database according to the characteristics of each data domain indicated by reference numeral 405 .

According to various example embodiments, in operation 303 , the server device 100 may obtain architecture information about a data service structure between the architecture frontend and the backend.

For example, the data service structure between the front end and the back end may mean a structure for serving data requested by the user side management part from the database side management part according to the user's UI/UX connection, and the like. In particular, in the case where the service provided by the server device 100 corresponds to electronic commerce, it may be based on the microservice architecture (MSA), wherein by corresponding to the front end related to the customer page One of the specific back-end side of the client page domain is responsible for the data domain as the goal to serve various data required by the client page, and for MSA, it is necessary to provide a core logic structure 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, duplication of code can increase and manage Difficult problem. Therefore, it is necessary to prevent the core logic structure from being fragmented according to each client page field or data field, and for this purpose, the data service structure (which is the object of the structure information obtained by the server device 100 according to operation 303) corresponds to the structure through A data service structure that prevents fragmentation by extensibility corresponding to different client page domains or data domains.

That is, based on the master data service structure for the data service, the data service structure (which is the target of the schema information obtained by the server device 100 according to operation 303) can be followed to make it possible to correspond to additional data of various client page domains or data domains The service structure is implemented in such a way that it can be extensible for different features of the client page domain or the data domain.

For example, the schema information obtained by the server device 100 according to operation 303 may include master schema information for constructing a master data service structure corresponding to one of the data services used to execute a data service between the front end and the back end. Basic data service structure. For example, when building a master data service structure between a front end and a back end based on master structure information, data requested by the front end side can be provided from the back end side. This master data service structure can be implemented in the same manner as in 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 for the master data service structure may include a plurality of data queues 503 corresponding to a plurality of backend data domains, and for storing data through a plurality of A common storage 505 of data transferred by the data queue and recalls from the storage the data requested by the front end and transmits it to a common service layer 507 of the front end.

In the master 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 may refer to a data queuing line that performs the functions of receiving and storing data provided from the transmitting unit, waiting until the stored data is transmitted to the receiving unit, and transmitting the stored data to the receiving unit. Among the plurality of data queues 503, one data queue corresponds to a backend data domain or one or more backend data domains, can receive data provided from the corresponding backend data domain and store it and then queue it, And it can send the data stored in cycle according to the data update of the storage to the storage side. That is, the data queue 503 may play a role of queuing data received from the backend data domain side and delivering the data to the storage side according to the update cycle of the storage side.

In addition, in the master data service structure 501, the storage can receive and store various data of the database through a plurality of data queues. Storage can mean the same or similar data storage space that stores and manages data in the database, so that the service layer can call the request data from the front end only by accessing the storage and without accessing the back-end data field. Serve. In the common storage 505, the storage can receive and store the data of the database managed by the back-end data domain, and specifically, there is a data queue between the back-end data domain and the storage, and the data queue The data from the database of the data domain is received and stored, and the memory can receive the data stored in the data queue according to a specific cycle. The service layer can obtain the desired data by calling the desired data to the storage for storing the received data in this way. That is, the common storage 505 can receive the data of the database managed in the 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 desired data by calling the desired data. The service layer may perform one of the functions of invoking various data requested from the storage through the plurality of client page domains included in the front end. In the common service layer 507, the service layer can be requested to call specific data from the client page corresponding to the front end, can access the storage and obtain the data requested as the call target by calling the data, and can obtain the desired data when Transmission back to the front side.

For example, the schema information obtained by the server device 100 according to operation 303 may include the first additional schema information of a first additional data service structure for schema addition to the master data service structure or the schema information for schema addition to the master data service structure. 1. The second additional structure information of the second additional data service structure. For example, 1) when the first additional data service structure is constructed between the front end and the back end based on the first additional structure information, the 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 the second additional data service structure is constructed between the front-end and the back-end based on the second additional structure information, the data requested from the front-end side is provided from the back-end side in a way different from the main data service structure, 3) when based on the first An additional structure information and a second additional structure information This can also be the same when both the first additional data service structure and the second additional data service structure are structured between the front end and the back end. Such a first additional data service structure and a second additional data service structure can be implemented in the same manner as in FIG. 6 to FIG. 8 .

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

A first additional data service structure 601 may include various components for data services. As an element for the first additional data service structure, the first additional data service structure 601 may include: a cache area 603, which is relatively contained in the storage when the specific data is updated and the updated specific data is confirmed in the storage Specific data in at least some of the data in the cache area is obtained from the storage and stored at least some of the data contained in the data stored in the storage; an update data queue (notification queue) 605 for storing Update the specific data and send it to the cache area; and a cache update manager (cache invalidator) 607, which manages to send the update specific data to the cache area through the update data queue.

In the first additional data service structure 601, the cache may obtain and store some of the data stored in the memory from the memory. In the program where the service layer accesses the memory and calls the desired data, the cache area can mean a separate data storage space for storing some data stored in the memory so that the service layer can easily access the memory for due This facilitates easy data access on the service layer side for reasons such as frequent calls from the service layer side for data that is the target of calls or prevents a problem of memory delays that can result from large amounts of data being called to memory. The cache 603 is located between the storage and the service layer, and the service layer can transfer the desired data to the front end by first calling the desired data from the cache before calling the desired data from the storage. If the service layer confirms that the desired data is not in the cache (because the desired data is not stored in the cache), the service layer can recall the desired data from the storage and transmit it to the front end.

Like the cache area 603, if the cache area that is structured to obtain and store some data stored in the memory is located between the memory and the service layer, then when the specific data stored in the cache area is in the backend data field When updating on the side, the memory can obtain and store specific data corresponding to the specific data update through the data queue, but if the cache area does not immediately verify whether the specific data is updated, it may appear that the memory stores the update specific data and the cache area Save one of the issues with not updating specific data. To prevent this problem, there is a need to check and manage updates to the data stored jointly in memory and cache, and the update notification queue 605 can play this role.

When updating data is identified and managed on the back-end data domain side for data stored in memory, the updated data is delivered and stored in a data queue of the plurality of data queues associated with the corresponding data and then based on the A specific cycle of the update cycle of the memory to transfer to the memory. At this time, if the data is stored in both the storage and the cache as described above, when the storage receives updated data, the cache must also receive the updated data in the same way and therefore it should be designed so that the updated Data may be delivered to the update notification queue as it is stored in memory. Based on this design, the update notification queue can keep the update data, and when the data updated according to the update cycle of the storage is identified in the storage and update data queue, it can instruct the cache update manager 607 to update the data through the update data queue Updates are sent to the cache.

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

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

7 is a diagram illustrating a state in which a second additional data service structure is added and structured 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 requiring real-time update management. In the second additional data service structure, among the data stored in the database, it is determined that the data that needs to be updated immediately may include: a real-time cache area 703, which is related to the corresponding data through one of the plurality of data queues The specific data queue acquires and stores real-time update data for corresponding data; 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 the data stored in the multiple data queues from the multiple data queues based on a near-real-time cycle, and identify the data that need real-time update management. 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 item inventory or promotional discount prices reflecting real-time updates) can be identified in advance, and in the plural corresponding to the back-end data domain In the data queue, when the 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 requiring real-time update management, the data queue related to the corresponding data can respond to the corresponding data to identify the updated data in real time, and the data queue transmits the real-time updated data to the real-time cache area. From the perspective of a data queue, the data held by the data queue is transmitted to the storage according to the update cycle of the storage, but if there is any data identified as requiring real-time update management, the real-time update related to the corresponding data Data can be transferred to the real-time cache on a near real-time 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 the cache area cannot store real-time update data in real time can be prevented. In addition, like the real-time cache manager 705, a real-time cache manager is separately structured 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 the data that needs to be updated immediately, the service layer can call the corresponding data from the real-time cache area based on whether the required data corresponds to the data that needs to be updated immediately and store it transmitted to the front end.

At this time, it is shown in FIG. 7 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 In , the service layer can call the required data through the direct access memory instead of the cache area.

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 structured between a front end and a back end.

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

With regard to Fig. 8, if the corresponding data corresponds to the data that needs to be updated immediately, then the service layer calls the corresponding data from both the real-time cache area and the cache area based on whether the required data corresponds to the data that needs to be updated immediately, and by identifying The real-time cache and information such as timescales and the like contained in the data called from the cache are used to transfer the latest data in the called data to the front end. On the other hand, if the corresponding data does not correspond to the data that needs to be updated in real time, the service layer calls the corresponding data from the cache area and transmits it to the front end, and if the corresponding data cannot be called from the cache area, it accesses the storage , call the corresponding data and transmit it to the front end. To this end, the server device 100 may perform an operation of obtaining information on whether the data requested by the front end (ie, the data desired by the service layer) corresponds to the data requiring immediate updating.

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

For example, there may be a case where specific material requested from the front end is requested from the front end in the form of a data set including a plurality of materials (including specific data) rather than in the form of a single material. If the front end requests a data set containing multiple data and confirms that the specific data contained in the multiple data is requested, only if all the multiple data can be called by the service layer from the storage, cache area or real-time cache area, Only certain data can be structured to be transmitted from the service layer to the front end.

That is, since a data set including plural data is requested from the front end in many cases in order to utilize all plural data in a client page or a specific area of the client page, it is possible to use only if all the data contained in the data set Multiple data included in the data set are only allowed to be transmitted to the front end when the data can be called to prevent data omission. For example, when a data set containing information such as an item's real-time inventory, 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 requiring real-time updates will be retrieved from the real-time The cache is called 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, even if the real-time inventory data is correctly called from the real-time cache, it cannot be transferred to front end.

In order to manage the above-mentioned data set type request, identification information corresponding to the data set may be determined and structured for a plurality of data included in the data set. A plurality of data contained in a data set share a piece of identification information corresponding to the data set, and based on this identification information, it can be confirmed that all the plurality of data contained in the data set are called from memory, cache area or real-time cache area , and can prevent data omission.

For example, the schema information obtained by the server device 100 in operation 303 may include information for interacting the first additional data service structure and the second additional data service structure with the main data service structure. As described above with reference to FIGS. 5 to 8 , the first additional data service structure and the second additional data service structure correspond to structures that provide data that interacts with the main data service structure, so even if an additional data service structure is added, using The interaction information that the frameworks interact with each other so that the data service can be executed smoothly may be included in the framework information obtained by the server device 100 in operation 303 .

For example, in operation 303, the server device 100's operation of obtaining schema information may include an operation of obtaining schema information, wherein the first additional schema information or the second additional schema information is optionally or adaptively included such that the first additional data service The structure or the second additional data service structure may be further structured according to the backend data domain corresponding to the service domains of various types forming the service. Operations may be performed as described in detail with reference to FIG. 9 .

FIG. 9 is a diagram illustrating an operation method in which the server device 100 for building a data service structure obtains structure information according to various example embodiments. FIG. 9 may correspond to a detailed operation method in which the server device 100 obtains the architecture information in operation 303 of FIG. 3 .

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

In operation 905, the server device 100 may identify the first information on whether the first additional data service structure will be constructed and the information on whether the second additional data service structure will be The second information to be framed. In operation 907, the server device 100 may obtain the first additional architecture information for adding the first additional data service structure or the second information for adding the second additional data service structure according to the first information and the second information. Schema information for additional schema information.

Since the back-end data domain related to the requested data in a specific service domain is likely to be a part of the entire back-end data domain, by determining whether some related back-end data domains need the first additional data service structure or the second additional data service The structure is used for data service, and the structure information determined to include the first additional structure information or the second additional structure information can be obtained from the server device 100 . Through this structured information acquisition operation of the server device 100, a data service structure can be designed to optimize the data services of some back-end data domains corresponding to a specific service domain.

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

Component symbol 1001 indicates schema information for a data service structure and indicates a selection option associated with schema for a main data service structure, a first additional data service structure and/or a second additional data service structure, And the component symbol 1003 indicates information related to each service domain, which may include information to confirm which backend data domains can match each service domain or whether the data service needs a first additional data service structure or a second additional data service Structure-related information and the like.

According to the information indicated by the element symbol 1003, a corresponding back-end data domain can be determined differently for each service domain indicated by the element symbol 1005, and as described above, when the corresponding back-end data domain changes, it can be as indicated by 1007 Change the data service structure of each service domain as an instruction. 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 particular backend data domain (catalogue, seller, subscription order), it can be confirmed that both a first additional data service structure and a second additional data service structure are added to the master data service structure And framed, and in a comment field corresponding to a different backend data field (member), it can be confirmed that only the first additional data service structure is added and framed to the main data service structure and framed.

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 a configuration for each service domain or corresponding to each service domain. The scalability of the data service of a back-end data domain, and the effectiveness of the data service can be improved by applying an optimal data service structure to each service domain or a back-end data domain corresponding to each service domain.

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 structure information.

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

For example, in operation 305, the data to be served requested from the front end may be data requested from a first client page corresponding to a first client page domain among the plurality of client 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 that stores real-time update data in a second additional data service structure that includes a real-time cache, the service layer has erroneous data from the failed real-time cache and will It may be more appropriate to provide users with a customer experience than providing users with previous information that is not updated in real time. Therefore, the server device 100 can isolate the dead real-time cache area by blocking the access path based on the circuit breaker to prevent the service layer from accessing the real-time cache area, and in this case, the service layer can serve from the cache area or The memory is not updated in real time but there is no error data.

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

For example, the data service structure configured by the server device 100 according to operation 305 may correspond to one data service structure among the plurality of data service structures existing between the front end and the back end. In other words, as shown in FIG. 11 , a 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 structuring a plurality of independent data service structures in this manner and having each data service structure correspond to a different client page domain, the server device 100 can be designed to correctly serve data for another client page domain, even when targeting a specific client page domain. A problem occurred in the domain's data service structure.

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 element symbols 1101 and 1103 are constructed between the front end and the back end of FIG. 11 , and the data service structure corresponding to element symbol 1101 is used to serve some of the plurality of client page domains data, and the data service structure corresponding to component symbol 1103 is used to serve data for other client page domains. By architecting multiple data service structures as shown in Figure 11, even if a data service for a particular client page domain becomes infeasible due to a problem with one data service structure, another data service structure is different Information on customer page domain services is also available.

Specifically, among the plurality of customer page domains, there may be some customer page domains that are of high importance to customer experience, such as a customer page domain for an item search page and a customer page domain for an item detail page domains and the like, and a data service structure of element number 1101 can be structured as a critical service path (CSP) for some customer page domains described above with high importance. Conversely, the data service structure for component notation 1103 can be structured as a non-CSP (N-CSP) for the remaining customer page domains that are not very important to the user experience, such as the customer page domain for item category pages and for The customer page domain of the My Page associated with the user profile.

The server device 100 concurrently and independently constructs the data service structure for the component symbol 1101 of the CSP and the data service structure for the component symbol 1103 of the N-CSP, so that it is used for the data service of other client page domains having high importance Structures can still be designed for data services, even though a problem occurs with data service structures for non-critical client page fields. In addition, when a problem occurs in the data service structure of the component symbol 1101 for the client page domain with high importance, the server device 100 can be designed so that the high importance client page domain can be served by using the data service of the component symbol 1103 structure to serve data to supplement data services for high-importance customer page domains.

According to the above example embodiments, 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 perform an operation based on the data service structure of FIG. 3 to FIG. 11 can be combined in various forms.

The exemplary embodiments of the present invention disclosed in the specification and drawings are only provided 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, those skilled in the art to which the present invention pertains 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 operated in combination with each other as needed. For example, all example embodiments of the invention may be implemented by a system in which components are combined with each other.

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

Thus, in a certain aspect, various example embodiments of the present invention can be embodied as computer readable codes on a computer readable recording medium. A computer readable recording medium is any data storage device that can store 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 tapes, floppy disks, optical data storage devices, and carrier waves (such as transmission of data via the Internet and the like). The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion. In addition, the functional programs, codes, and code segments for achieving various example embodiments of the present invention can be easily interpreted by programmers familiar with the field of application of the present invention.

In addition, it should be understood that the apparatuses and methods according to various example embodiments of the present invention may be implemented in the form of hardware, software or a combination of hardware and software. This software may 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 is optically or magnetically writable and readable by a machine (such as a computer), such as a compact disc (CD), DVD, magnetic disk or tape, and the like. Methods according to various example embodiments of the present invention may be implemented by a computer including a controller and a memory or a vehicle including such a memory or a computer, it being understood that such a memory system is suitable for storing information including An example of a machine-readable storage medium for one or more programs of instructions of example embodiments of the invention.

Therefore, the present invention includes a program (including codes for implementing the apparatus or method described in the claims of this specification) and a machine (computer and the like) readable storage medium storing the program. In addition, such a program may be electronically transmitted through any medium, such as a communication signal transmitted through a wired or wireless connection, and the present invention properly includes equivalents thereof.

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 the specification and drawings are presented only as specific examples to easily explain the technical contents of the present invention and to help understanding of the present invention, and It is not intended to limit the scope of the invention. In addition, the above-described example embodiments according to the present invention are only illustrative, and those skilled in the art will understand therefrom that various modifications and equivalent ranges of the embodiments are possible. Therefore, the scope of the present invention should be defined by the scope of the following claims.

100: server device 200: device 210: input/output unit 220: communication component 230: Storage 240: Processor 301: Operation 303: Operation 305: Operation 401: Customer Page Domain 403: backend data field 405: data field 501: Master data service structure 503: data queue 505: common storage 507: common 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: instant cache area 705: Instant 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

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

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 flowchart illustrating an operation method of a server device 100 for building a data service structure according to various example embodiments.

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

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.

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

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

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 structured between a front end and a back end.

FIG. 9 is a flowchart illustrating an operation method in which the server device 100 for building a data service structure obtains structure information according to various example embodiments.

FIG. 10 is a diagram illustrating an example of a data service structure according to a backend data domain architecture 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 architecture by providing a service with an electronic device, the method comprising: Identify information about a front end comprising a plurality of customer page domains for the service and information about a back end comprising a plurality of back end data domains associated with a database used for the service; obtain architectural information for architecting a data services structure between the front end and the back end; and Based on the schema information, schemating the data service structure includes a master data service structure for serving data requested by the front end. The method as claimed in item 1, wherein the schema information includes master schema information used to structure the master data service structure, and The master data service structure includes: a plurality of data queues corresponding to the plurality of backend data fields; a memory in which data transmitted through the plurality of data queues is stored; and A service layer invokes the request data from the storage and transmits the request data to the front end. The method of claim 2, wherein the architecture information further includes: first additional schema information for schemating a first additional data service structure added to the master data service structure; or The second additional schema information is used to schema a second additional data service structure added to the master data service structure. The method of claim 3, wherein the first additional data service structure includes: a cache area structured to obtain from the storage and store at least a portion of the data contained in the data stored in the storage; an updated data queue structured to transmit updated first data to the cache upon identifying updated first data in the memory corresponding to first data contained in the at least a portion of the data; and a cache update manager structured to manage the updated first data transmitted to the cache area through the update data queue, and The second additional data service structure includes: a real-time cache area structured to obtain and store real-time updated second data corresponding to the second data through a specific one of the plurality of data queues associated with the second data, the second data is determined to require immediate updating of the information stored in the database; and A real-time cache update manager structured to manage the real-time update second data transmitted to the real-time cache area through the specific data queue. The method of claim 4, wherein the schema information includes information for enabling the first additional data service structure and the second additional data service structure to interact with the master data service structure. The method of claim 4, wherein when updating the first data, based on a first cycle corresponding to an update cycle of the memory, through a data queue related to the first data among the plurality of data queues row transmits the updated first data to the memory, and instructing the cache update manager to transmit the updated first data to the cache area through the update data queue when the update first data is identified in the storage and the update data queue according to the first cycle . The method of claim 4, wherein structuring the data service structure includes structuring the data service structure based on the first additional structure information including the master data service structure and the first additional data service structure, 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 identified in the cache area, the service layer recalls the request data from the storage and transmits the request data to the front end. The method of claim 4, wherein the 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 according to claim 4, wherein when the updated first data is identified in the storage and the unupdated first data is identified in the cache area, update request information for the first data is sent by the service layer transmission. The method of claim 4, wherein when the second data is updated, based on a second period corresponding to real time, the real-time updated second data is transmitted to the real-time cache area through the specific data queue. The method of claim 4, wherein structuring the data service structure includes structuring the data service structure based on the second additional structure information including the master data service structure and the second additional data service structure, and Based on whether the requested data corresponds to data requiring real-time updating, the service layer invokes the requested data from the real-time cache area and transmits the requested data to the front end. The method of claim 4, wherein structuring the data service structure includes structuring the data service structure based on the first additional schema information and the second additional schema information, including the master data service structure, the first additional data service structure, and the The second additional data service structure, When the requested data corresponds to data that requires real-time updates, the service layer invokes the requested data from both the cache and the real-time cache, and Transmitting to the front-end the most recent of the data invoked by the service layer in the cache and the real-time cache. The method according to claim 12, wherein if the requested data does not correspond to data that needs to be updated immediately, the service layer calls the requested data from the cache area and transmits the requested data to the front end. The method of claim 12, further comprising: Obtain information on whether the requested data corresponds to data that needs to be updated in real time. The method according to claim 12, wherein when the front end requests a data set including a plurality of data and the requested data is included in the plurality of data, based on all the plurality of data, the service layer stores the data in the storage, the cache call in the fetch area or the instant cache area to transfer the request data to the front end. 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 the plurality of data calls from the storage, the cache area or the real-time cache area. The method of claim 4, wherein obtaining the structure information includes: Identify information about a first service domain associated with the service; identifying information about one or more of the plurality of backend data domains 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 is to be framed and second information about whether the second additional data service structure is to be framed; and The framework information determined to include the first additional framework information or the second additional framework information is obtained based on the first information and the second information. The method of claim 1, wherein the requested data is requested from a first client page domain corresponding to a first client page domain included in the plurality of customer page domains. An electronic device for constructing a data service structure related to a service, the electronic device comprising: a processor; and one or more memories in which one or more instructions are stored, Wherein the one or more instructions, when executed, control the processor to perform: Identify information about a front end comprising a plurality of customer page domains for the service and information about a back end comprising a plurality of back end data domains associated with a database used for the service; obtain architectural information for architecting a data services structure between the front end and the back end; and Based on the schema information, schemating the data service structure includes a master data service structure for serving data requested by the front end.

Images