IP Library Patent Application 14335541
Patent Application
App. No. 14/335,541

DATACENTER EVENT STREAM PROCESSING IN A NETWORK-BASED COMMUNICATION SYSTEM

Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US None
App. No.
14/335,541
Abstract

The present application details exemplary methods and systems for processing an event stream at one or more datacenters within a network-based communication system. For example, a datacenter can detect an event that occurs within the network-based communication system. Upon detecting the event, the datacenter can create an event message and send the event message to other datacenters in the network-based communication system. Each datacenter that receives the event message from the datacenter can process the event message to obtain event information and can store the event information in association with a context, such as a user account.

Claims (48)

1 . A method comprising:

receiving a first event message associated with a first context from a first datacenter;

placing the first event message in an event queue;

receiving a second event message associated with a second context from a second datacenter;

placing the second event message in the event queue;

updating, by at least one processor, state information corresponding with the first context upon processing the first event message in the event queue; and

updating the state information corresponding to the second context upon processing the second event message in the event queue.

2 . The method of claim 1 , wherein the first context and the second context are the same user account.

3 . The method of claim 1 , wherein the first context and the second context are the different contexts.

4 . The method of claim 1 , wherein the first event and the second event are the same event type.

5 . The method of claim 1 , wherein the second event has a higher priority than the first event.

6 . The method of claim 5 , wherein the second event is processed before first event.

7 . The method of claim 1 , further comprising:

sending a first confirmation event message to the first datacenter upon processing the first event message; and

sending a second confirmation event message to the second datacenter upon processing the second event message.

8 . The method of claim 1 , further comprising processing events in the order in each event is placed in the event queue.

9 . The method of claim 1 , further comprising processing events based on a timestamp included in each event message.

10 . The method of claim 1 , further comprising increasing processing capabilities when the number of events in the event queue surpass a predetermined number.

11 . A method comprising:

detecting a first event associated with a first context;

creating, by at least one processor, a first event message that includes first event information based on the first event;

providing the first event message to an event queue;

receiving a second event message from a second datacenter that includes second event information based on a second event associated with a second context;

providing the second event message to the event queue;

processing the first event message and the second event message in the event queue;

updating state information associated with the first context based on the first event information upon processing the first event message; and

updating state information associated with the second context based on the second event information upon processing the second event message.

12 . The method of claim 11 , further comprising:

sending the first event message to the second datacenter; and

receiving a confirmation from the second datacenter that the first event message has been processed at the second datacenter.

13 . The method of claim 11 , wherein the first event is triggered by user action.

14 . The method of claim 11 , further comprising generating an archival copy of the state information associated with the first context.

15 . The method of claim 14 , further comprising generating the archival copy of the state information associated with the first context after a predetermined amount of time has elapsed.

16 . The method of claim 14 , further comprising generating the archival copy of the state information associated with the first context after a predetermined number of processing updates occur to the state information associated with the first context.

17 . The method of claim 14 , further comprising receiving a second copy of the state information associated with the first context from the second datacenter.

18 . The method of claim 17 , further comprising comparing the copy of the state information associated with the first context with the second copy of the state information associated with the first user account received from the second datacenter.

19 . A system comprising:

at least one processor; and

at least one non-transitory computer readable storage medium storing instructions thereon that, when executed by the at least one processor, cause the system to:

detect a first event associated with a first user account;

create a first event message that includes first event information based on the first event;

provide the first event message to an event queue;

receive a second event message from a second datacenter that includes second event information based on a second event associated with a second user account;

provide the second event message to the event queue;

process the first event message and the second event message in the event queue;

update state information associated with the first user account based on the first event information upon processing the first event message; and

update state information associated with the second user account based on the second event information upon processing the second event message.

20 . The system of claim 19 , wherein the first event is triggered by a system event.

Assignments (5)
RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 045954/0060 Recorded Aug 31, 2020
From: JPMORGAN CHASE BANK, N.A.
To: JIVE COMMUNICATIONS, INC.
Reel/Frame 053650/0944 →
SECURITY INTEREST Recorded May 31, 2018
From: JIVE COMMUNICATIONS, INC.
To: JPMORGAN CHASE BANK, N.A., ADMINISTRATIVE AGENT
Reel/Frame 045954/0060 →
RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY COLLATERAL AT REEL/FRAME NO. 035759/0382 Recorded May 23, 2018
From: SILICON VALLEY BANK
To: JIVE COMMUNICATIONS, INC.
Reel/Frame 046220/0335 →
SECURITY INTEREST Recorded Jun 2, 2015
From: JIVE COMMUNICATIONS, INC.
To: SILICON VALLEY BANK
Reel/Frame 035759/0382 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 18, 2014
From: ZOURZOUVILLYS, THEO PETER
To: JIVE COMMUNICATIONS, INC.
Reel/Frame 033345/0764 →