Events account for native app event sharing

Patent metadata

Field	Value
Publication number	US-12250249-B2
Application number	US-202418604252-A
Country	US
Kind code	B2
Filing date	Mar 13, 2024
Priority date	Mar 28, 2023
Publication date	Mar 11, 2025
Grant date	Mar 11, 2025

Abstract

Embodiments of the present disclosure provide a region-specific events account that is used as a central place to store the events shared by consumers of shared applications in that region. For each of a set of provider accounts in a first region, a global account object corresponding to the provider account is replicated to a second region to establish a replicated global account object in the second region. An account data persistence object (DPO) of a first provider account of the set of provider accounts is modified to designate the first provider account as an events account. The events account is a central location within the second region where execution information generated by execution of applications shared with consumer accounts in the second region is stored. The replicated global account object corresponding to the first provider account is updated to designate the first provider account as the events account.

First claim

What is claimed is:

1. A method comprising:
for each of a set of provider accounts in a first region, replicating a global account object corresponding to the provider account to a second region to establish a replicated global account object in the second region; and
transmitting a first message to the second region to designate a first provider account of the set of provider accounts as an events account of the second region, the first message having logic to:
modify, by a processing device, an account data persistence object (DPO) of the first provider account to designate the first provider account as the events account, wherein the events account is a central location within the second region where execution information generated by execution of applications shared with consumer accounts in the second region is stored; and
update the replicated global account object corresponding to the first provider account to indicate that the first provider account has been set as the events account.

2. The method of claim 1 , further comprising:
transmitting a second message to the first region to update a status of the global account object corresponding to the first provider account as the events account.

3. The method of claim 1 , further comprising:
executing, by a consumer account of the second region, an application shared by a provider; and
storing, in the replicated global account object corresponding to the first provider account, first execution information generated from the execution of the application by the consumer account of the second region.

4. The method of claim 1 , wherein modifying the account DPO comprises:
updating an entry of the account DPO corresponding to the first provider account with a first timestamp indicating a current time.

5. The method of claim 1 , wherein updating the replicated global account object corresponding to the first provider account comprises:
updating an entry of the replicated global account object corresponding to the first provider account with a first timestamp indicating a current time.

6. The method of claim 1 , further comprising:
transmitting to the second region, a second message to designate a second provider account of the set of provider accounts as the events account by:
updating an entry of an account DPO corresponding to the second provider account with a second timestamp indicating a new current time to designate the second provider account as the events account;
updating an entry of the replicated global account object corresponding to the second provider account with the second timestamp indicating the new current time; and
transmitting a third message to the first region to update a status of the global account object corresponding to the second provider account as the events account.

7. The method of claim 6 , further comprising:
in response to a workload executing in the second region attempting to resolve the events account, comparing the first and second timestamps; and
in response to determining that the second timestamp is later in time, resolving the second provider account as the events account.

8. The method of claim 6 , further comprising:
in response to a request to remove the second provider account's designation as the events account, scanning each replicated global account object to identify each provider account having a timestamp that is less recent than the second time stamp;
grouping each identified provider account;
transmitting a fourth message to reset an entry of the account DPO corresponding to the first provider account to zero and reset an entry of the replicated global account object corresponding to the first provider account to zero; and
transmitting a fifth message to the first region to update the status of the global account object corresponding to the first provider account as not the events account.

9. The method of claim 8 , further comprising:
transmitting a sixth message to reset an entry of the account DPO corresponding to the second provider account to zero and reset an entry of the replicated global account object corresponding to the second provider account to zero; and
transmitting a seventh message to the first region to update the status of the global account object corresponding to the second provider account as not the events account.

10. A system comprising:
a memory; and
a processing device operatively coupled to the memory, the processing device to:
for each of a set of provider accounts in a first region, replicate a global account object corresponding to the provider account to a second region to establish a replicated global account object in the second region; and
transmit a first message to the second region to designate a first provider account of the set of provider accounts as an events account of the second region, the first message having logic to:
modify an account data persistence object (DPO) of the first provider account to designate the first provider account as the events account, wherein the events account is a central location within the second region where execution information generated by execution of applications shared with consumer accounts in the second region is stored; and
update the replicated global account object corresponding to the first provider account to indicate that the first provider account has been set as the events account.

11. The system of claim 10 , wherein the processing device is further to:
transmit a second message to the first region to update a status of the global account object corresponding to the first provider account as the events account.

12. The system of claim 10 , wherein the processing device is further to:
execute, by a consumer account of the second region, an application shared by a provider; and
store, in the replicated global account object corresponding to the first provider account, first execution information generated from the execution of the application by the consumer account of the second region.

13. The system of claim 10 , wherein to modify the account DPO, the processing device is to:
update an entry of the account DPO corresponding to the first provider account with a first timestamp indicating a current time.

14. The system of claim 10 , wherein to update the replicated global account object corresponding to the first provider account, the processing device is to:
update an entry of the replicated global account object corresponding to the first provider account with a first timestamp indicating a current time.

15. The system of claim 10 , wherein the processing device is further to:
transmit to the second region, a second message to designate a second provider account of the set of provider accounts as the events account by:
update an entry of an account DPO corresponding to the second provider account with a second timestamp indicating a new current time to designate the second provider account as the events account;
update an entry of the replicated global account object corresponding to the second provider account with the second timestamp indicating the new current time; and
transmit a third message to the first region to update a status of the global account object corresponding to the second provider account as the events account.

16. The system of claim 15 , wherein the processing device is further to:
in response to a workload executing in the second region attempting to resolve the events account, compare the first and second timestamps; and
in response to determining that the second timestamp is later in time, resolve the second provider a

Assignees

• Snowflake Inc

Inventors

• Carru Damien
• Chu Pui Kei Johnston
• Jagtap Unmesh
• Ke Xiaodi
• Muralidhar Subramanian
• Pan James

Classifications

• H04L63/102

  Entity profiles · CPC title

• G06F16/235

  Update request formulation · CPC title

• G06F11/079

  Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36) · CPC title

• H04L67/30 Primary

  Profiles · CPC title

• H04L67/125

  involving control of end-device applications over a network · CPC title