Distributed Network Event Management via Semantic Replication

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Centralized event management in database grids introduces delays and inefficiencies, and creates a single point of failure, as all writes must go through a master node, leading to bandwidth-intensive data propagation and potential bottlenecks.

Innovation Solution

Implementing a distributed database system with semantic replication and provisional write authority, where network appliances can detect and propagate network event information independently, reducing latency and enhancing scalability by allowing members to write to their local databases without immediate master node approval.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If centralized event management is implemented with a single master node, then system control and coordination are simplified, but system reliability deteriorates due to single point of failure

Engineering Contradiction:

Improveevent management structureVSAvoidsystem reliability

Core Design Contradiction:

Device complexityVSReliability

Solution Approach 1:

The patent segments the centralized event management function into distributed components across multiple nodes. Each node maintains local event information and can independently manage events, eliminating the single point of failure while maintaining coordination through versioned database replication.

Inventive Principle:

Principle #1Segmentation

2Stability of the object's composition

If all database writes must go through the master node, then data consistency is maintained, but system performance deteriorates due to bandwidth-intensive data propagation and bottlenecks

Engineering Contradiction:

Improvedata consistencyVSAvoidsystem performance

Core Design Contradiction:

Stability of the object's compositionVSProductivity

Solution Approach 1:

The patent applies preliminary action by allowing nodes to perform writes locally before master node approval. Nodes can detect events, update local database versions, and propagate changes asynchronously, eliminating the bottleneck of requiring master node approval for every write operation while maintaining consistency through version tracking.

Inventive Principle:

Principle #10Preliminary action

3Device complexity

If centralized event management is used, then event coordination is simplified, but response time deteriorates due to delays in event detection and propagation

Engineering Contradiction:

Improveevent coordinationVSAvoidresponse time

Core Design Contradiction:

Device complexityVSLoss of time

Solution Approach 1:

The patent segments event detection and management capabilities to individual nodes. Each node can independently detect events locally and update its database version immediately, eliminating the delay of centralized event detection while maintaining coordination through versioned replication to other nodes.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS8060534B1Event management

Publication Date: 2011.11.15 INFOBLOX INC

AI summary

Managing network event information from a plurality of network appliances is disclosed. Each network appliance provides a network service and each has a version of a common database. Managing includes detecting network event information at a first network appliance, updating a version of the common database on the first network appliance with the network event information, and propagating the network event information to other versions of the database on other network appliances.