US 12,153,584 B2
Complex event processing on server-less framework
Vikram Tatavarthi, Herndon, VA (US); Pradeep Khandelwal, Vienna, VA (US); Kristaps Berzinch, Arlington, VA (US); Pooja Mulik, Ashburn, VA (US); Jonathon Snyder, Alexandria, VA (US); Jeremy Hanford, Reston, VA (US); Sandeep Kumar, Ashburn, VA (US); and Sujay Nagendrappa Beesnalli, Herndon, VA (US)
Assigned to Capital One Services, LLC, McLean, VA (US)
Filed by Capital One Services, LLC, McLean, VA (US)
Filed on Mar. 29, 2021, as Appl. No. 17/216,411.
Prior Publication US 2022/0309068 A1, Sep. 29, 2022
Int. Cl. G06F 16/2455 (2019.01); G06F 9/54 (2006.01)
CPC G06F 16/24568 (2019.01) [G06F 9/542 (2013.01); G06F 16/24565 (2019.01)] 20 Claims
OG exemplary drawing
 
1. A computer-implemented method for server-less complex event processing (CEP), the computer-implemented method comprising:
hosting a plurality of server-less functions, the plurality of server-less functions including at least a first group of server-less functions, the first group of server-less functions including a driver function and at least one lookup function including a first lookup function, the plurality of server-less functions configured to execute only when associated data streams are received;
receiving data streams, the data streams including:
a first data stream, the first data stream including a plurality of discrete data packets, and
a second data stream, the second data stream including a plurality of discrete data packets,
wherein the first data stream is received at a different time than the second data stream;
processing the data streams, using the driver function and/or the at least one lookup function; and
publishing a CEP data stream based on the processing of the data streams using the driver function and/or the at least one lookup function, wherein the CEP data stream includes at least one discrete data packet of the first data stream and at least one discrete data packet of the second data stream, thereby enabling complex event processing to be performed using the plurality of server-less functions configured to execute only when associated data streams are received.