ZooKeeper Event Watching for Distributed Data Coordination

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In distributed systems, especially those handling large amounts of data, the lack of a distributed coordinator leads to high resource consumption when changing data, as applications need to read and update data from databases directly, which is inefficient.

Innovation Solution

Implementing a method where an application server performs event watching on a ZooKeeper server, receives information about changes in specific fields, updates the data accordingly, and provides the changed data to clients without altering the database, thereby reducing resource consumption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If a distributed coordinator (ZooKeeper) is used to manage data changes, then resource consumption is reduced, but device complexity increases

Engineering Contradiction:
Improveresource consumptionVSAvoidsystem complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The patent introduces a distributed coordinator (ZooKeeper server) as an intermediary component between the application server and the database. This mediator manages data change coordination, allowing the application server to efficiently track and respond to data modifications without directly handling complex database operations, thereby reducing overall resource consumption while maintaining manageable system complexity through specialized component division.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system is segmented into distinct functional components: the distributed coordinator (ZooKeeper server) handles coordination and change notification, the application server handles data processing and client requests, and the database handles data storage. This segmentation allows each component to specialize in specific tasks, improving efficiency and reducing resource consumption while the modular architecture keeps complexity manageable through clear separation of concerns.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If data is read and updated directly from the database without a distributed coordinator, then device complexity is reduced, but resource consumption increases

Engineering Contradiction:
Improvesystem complexityVSAvoidresource consumption
Core Design Contradiction:
Device complexityVSLoss of energy

Solution Approach 1:

The distributed coordinator performs preliminary actions by pre-processing data changes and generating change notifications before the application server needs to access the data. This preliminary action allows the application server to efficiently track only the necessary changes rather than reading and processing entire datasets, reducing resource consumption while maintaining relatively simple system architecture.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where the distributed coordinator monitors database changes and sends notifications back to the application server. This feedback loop allows the application server to respond efficiently to specific data changes without continuously polling or reading entire datasets, reducing resource consumption while keeping the system architecture relatively simple through event-driven communication.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20220300891A1Method for processing data of distributed coordination system and electronic apparatus therefor
Publication Date: 2022.09.22 COUPANG CORP
  • US20220300891A1 patent drawing
  • US20220300891A1 patent drawing
  • US20220300891A1 patent drawing

AI summary

Disclosed is a method in which an application server of a distributed system provides data, the method including performing event watching on a ZooKeeper server, receiving information related to a change of a first field included in first data from the ZooKeeper server according to a result of the event watching, reading the first data from a first storage when a request signal for the first data is input from a client, and changing a value of the first field included in the read first data on the basis of the information received from the ZooKeeper server and providing the first data with the changed value of the first field to the client.