Dynamically adjusting performance of materialized view maintenance

Patent metadata

Field	Value
Publication number	US-2021165789-A1
Application number	US-201916699530-A
Country	US
Kind code	A1
Filing date	Nov 29, 2019
Priority date	Nov 29, 2019
Publication date	Jun 3, 2021
Grant date	—

Abstract

The maintenance of a materialized view created and managed by a materialized view management platform may be dynamically adjusted. The performance of updates to a materialized view are monitored to trigger different events to make adjustments to the performance of subsequent updates. The materialized view management platform can adequately scale to handle changes to data sources as inputs to the maintenance of the materialized view, as well as make other adjustments handle various changes in the capability of the target data store to receive updates to the materialized view (e.g., target data store outages).

First claim

What is claimed is:

1 . A system, comprising:
at least one processor; and a memory, that stores program instructions that when executed by the at least one processor cause the at least one processor to implement a materialized view management platform, configured to:
create a materialized view from one or more of a plurality different data stores that the materialized view management platform is capable of accessing to store the materialized view in a target data store according to a definition for the materialized view;
monitor performance of updates to the materialized view in the target data store to detect an event to adjust the performance of updates to the materialized view;
in response to the detection of the event:
adjust the performance of updates to the materialized view based on the detected event, wherein the adjustment is to at least one of:
obtaining changes for the materialized view from the different data sources;
determining the updates to make to the materialized view; or
making the updates to the materialized view in the target data store.

2 . The system of claim 1 , wherein the detected event to adjust the performance of updates to the materialized view indicates that the target data store is unavailable, and wherein the adjustment to making the updates to the materialized view in the target data store comprises instructing a target connector for the target data store to buffer received updates to the materialized view.

3 . The system of claim 1 , wherein the adjustment to making the updates to the materialized view in the target data store comprises increasing or decreasing an update rate for performing updates to the materialized view in the target data store.

4 . The system of claim 1 , wherein the materialized view management platform is offered as part of a provider network and wherein at least one of the different data sources is another service offered by the provider network.

5 . A method, comprising:
monitoring performance of updates to a materialized view in a target data store received from one or more of a plurality of different data sources used to create the materialized view to detect an event to adjust the performance of updates to the materialized view; in response to detecting the event:
adjusting the performance of updates to the materialized view based on the detected event, wherein the adjustment is to at least one of:
obtaining changes for the materialized view from the different data sources;
determining the updates to make to the materialized view; or
making the updates to the materialized view in the target data store.

6 . The method of claim 5 , wherein the adjustment to obtaining the changes for the materialized view from the different data sources comprises increasing or decreasing a change capture rate for one or more of the different data sources.

7 . The method of claim 5 , wherein the adjustment to making the updates to the materialized view in the target data store comprises increasing or decreasing an update rate for performing updates to the materialized view in the target data store.

8 . The method of claim 5 , wherein the detected event to adjust the performance of updates to the materialized view indicates that the target data store is unavailable, and wherein the adjustment to making the updates to the materialized view in the target data store comprises instructing a target connector for the target data store to buffer received updates to the materialized view.

9 . The method of claim 5 , wherein the adjustment to determining the updates to make to the materialized view comprises increasing or decreasing maintenance events for performing updates to the materialized view in the target data store.

10 . The method of claim 5 , wherein the adjustment to determining the updates to make to the materialized view comprises assigning performance of an operation to a view maintenance processing node instead of one of the data sources in a maintenance plan that is executed to determine the updates to make to the materialized view.

11 . The method of claim 10 , wherein the detected event to adjust the performance of updates to the materialized view indicates that usage of the one data source exceeds a utilization limit.

12 . The method of claim 5 , wherein the detected event to adjust the performance of updates to the materialized view indicates that a lag between updates to the materialized view and changes at the data sources exceeds a threshold.

13 . The method of claim 5 , wherein the event is detected according to one or more performance criteria, and wherein the method further comprises receiving a request that specifies the one or more performance criteria.

14 . One or more non-transitory, computer-readable storage media, storing program instructions that when executed on or across one or more computing devices cause the one or more computing devices to implement a materialized view management platform that implements:
monitoring performance of updates to a materialized view in a target data store received from a plurality of different data sources used to create the materialized view to detect an event to adjust the performance of updates to the materialized view; in response to detecting the event:
adjusting the performance of updates to the materialized view based on the detected event, wherein the adjustment is to at least one of:
obtaining changes for the materialized view from the different data sources;
determining the updates to make to the materialized view; or
making the updates to the materialized view in the target data store.

15 . The one or more non-transitory, computer-readable storage media of claim 14 , wherein the adjustment to obtaining the changes for the materialized view from the different data sources comprises increasing or decreasing a change capture rate for one or more of the different data sources.

16 . The one or more non-transitory, computer-readable storage media of claim 14 , wherein the adjustment to making the updates to the materialized view in the target data store comprises increasing or decreasing an update rate for performing updates to the materialized view in the target data store.

17 . The one or more non-transitory, computer-readable storage media of claim 14 , wherein the detected event to adjust the performance of updates to the materialized view indicates that the target data store is unavailable, and wherein the adjustment to making the updates to the materialized view in the target data store comprises instructing a target connector for the target data store to buffer received updates to the materialized view.

18 . The one or more non-transitory, computer-readable storage media of claim 14 , wherein the adjustment to determining the updates to make to the materialized view comprises increasing or decreasing maintenance events for performing updates to the materialized view in the target data store.

19 . The one or more non-transitory, computer-readable storage media of claim 14 , wherein the adjustment to determining the updates to make to the materialized view comprises assigning performance of an operation to a view maintenance processing node instead of one of the data sources in a maintenance plan that is executed to determine the updates to make to the materialized view.

20 . The one or more non-transitory, computer-readable storage media of claim 14 , wherein the materialized view management platform is offered as part of a provider network and wher

Assignees

• Amazon Tech Inc

Inventors

• Deshpande Rohan
• Papakonstantinou Yannis
• Zaki Omer Ahmed
• Bharathy Karthik Gurumoorthy Subramanya
• Dugar Rajib
• Ummenthala Shivateja Reddy

Classifications

• G06F2201/80

  Database-specific techniques · CPC title

• G06F11/3495 Primary

  for systems · CPC title

• G06F11/3409

  for performance assessment · CPC title

• G06F16/2445 Primary

  Data retrieval commands; View definitions · CPC title

• G06F16/21

  Design, administration or maintenance of databases · CPC title