Edge Datastore Engine for Low-Latency Query Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content delivery networks (CDNs) face latency issues due to the need for network transmission delays to retrieve data from origin databases, and edge location scripts have limited capabilities, including inability to make network calls or access databases for security reasons.
Innovation Solution
Implementing a system with edge datastores that cache frequently requested data, allowing edge locations to process queries locally without network calls, using a datastore engine to translate queries and store data in a native format, and enabling event-triggered functions to access local tables for low-latency data retrieval and processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is retrieved from origin databases for each client request, then data freshness is maintained, but network transmission delays increase latency
Solution Approach 1:
The system pre-loads data from origin databases into edge datastores before client requests arrive. This preliminary action stores frequently accessed data locally at edge locations, enabling subsequent requests to be served from cached data without network transmission delays, thus resolving the contradiction between maintaining data freshness and reducing latency
Solution Approach 2:
The patent introduces an intermediary component (edge datastore) between the origin database and the client. This intermediary caches data locally at edge locations, allowing the system to serve requests from the intermediary rather than directly from the origin database, thereby reducing network transmission delay while maintaining data availability
2Adaptability or versatility
If edge location scripts are given full network access to access databases, then functionality is improved, but security risks increase
Solution Approach 1:
The system implements local quality by providing scripts with access to local edge datastores rather than granting universal network access. Each edge location has its own isolated datastore that scripts can access and modify, giving them the necessary functionality while containing security risks within the local scope and preventing unauthorized access to other parts of the system
3Productivity
If scripts execute with full database access permissions, then processing capability is improved, but system stability deteriorates due to potential errors
Solution Approach 1:
The patent applies local quality by isolating script execution to specific local datastores at edge locations. Scripts have full access permissions only to their designated local datastore, enabling high processing capability while preventing system-wide stability issues. Any errors or malicious actions are contained locally and cannot affect the broader system
Solution Approach 2:
The system introduces an intermediary layer (the edge datastore interface) between scripts and the database system. This intermediary provides controlled access permissions, allowing scripts to execute with high processing capability on local data while the intermediary mediates and contains any potential errors, preventing them from propagating and affecting system stability
Data Source
AI summary
A datastore engine at an edge location of a content delivery network (CDN) may perform low-latency query processing and data retrieval for multiple types of databases at one or more origin servers. When a client sends a query to the edge location, the datastore engine translates the query from a back-end database format into a native format of the local edge datastore. If the requested data is not there, then the datastore engine retrieves the data from the back-end table and inserted inserts the data into the local edge datastore. By using multiple queries over time to re-construct data from the backend database tables at the edge, the datastore engine may provide low-latency access to data from the backend database tables (avoiding the need to retrieve data from the back-end tables to serve subsequent queries).