Distributed Database External Services for Search Offloading

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional distributed databases lack additional capabilities beyond data storage and processing, limiting their functionality as datasets grow in size.

Innovation Solution

The integration of external services within a distributed database service that can interface with external service providers to perform additional or supplemental functions, enhancing the database's capabilities by outsourcing search results for further processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If distributed databases use sharding technique to store data across multiple servers, then storage capacity and search efficiency are improved, but functional capabilities remain limited

Engineering Contradiction:
Improvesearch efficiencyVSAvoidfunctional capabilities
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent introduces external services as intermediary components that extend the functionality of distributed databases. These external services act as mediators between the database system and additional capabilities, allowing the database to perform functions beyond basic data storage and retrieval without modifying the core database architecture. The external services receive queries from the database, process them, and return results, thereby expanding functional capabilities while maintaining the existing sharding-based storage efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If distributed databases process all operations internally, then data security and control are maintained, but computational burden on individual nodes increases

Engineering Contradiction:
Improvedata controlVSAvoidcomputational burden
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent applies segmentation by dividing computational tasks between internal database operations and external service processing. Routine data storage and retrieval operations remain internal to maintain security and control, while specific processing functions are segmented out to external services. This segmentation reduces the computational burden on individual database nodes while maintaining data control through authorized access mechanisms and result verification.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If external services are made available to all nodes, then functionality is enhanced, but system complexity and access control requirements increase

Engineering Contradiction:
ImprovefunctionalityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements universality by creating a standardized external service interface that can be accessed by different nodes based on their roles and authorization. Rather than implementing separate functionality for each node type, the system provides a universal access mechanism where coordinator nodes, worker nodes, and external services all interact through common protocols and authorization frameworks. This reduces system complexity while maintaining enhanced functionality across the distributed database.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12561328B2External services in distributed databases
Publication Date: 2026.02.24 CROWDSTRIKE
  • US12561328B2 patent drawing
  • US12561328B2 patent drawing
  • US12561328B2 patent drawing

AI summary

Computer nodes associated with a cluster store a distributed database. As the cluster provides a distributed database service, some or all of the nodes may interface with one or more external services. The external services may be specified by a service agreement, or the external services may be dynamically specified by a user/customer of the distributed database service. The external services may be available to any node of the cluster, or the external services may only be accessible to particular nodes and/or to particular cluster/service roles. In a mapreduce database framework, for example, the external services may be restricted to reducer/coordinator nodes. Whichever nodes are permitted, the nodes may use remote procedure calls to access external services.