Successfactors, Inc.

Sap Se

Baskaran Janarthanam

Dmitri Krakovsky

Abhijit Salvi

David Ragones

Abbas Raza

Ankur Bhatt

Divyesh Jain

Murali Mazhavanchery

Rajesh Prabhu

Sirisha Ayyagari

Some embodiments provide a system that includes a set of event publishers configured to publish events occurring on the event publishers. The system also includes a uniform event framework configured to receive, from an event publisher in the set of event publishers, an event notification indicating an event occurred on the event publisher and generate an event structure based on the event notification. The system further includes an event bus configured to receive the event notification from the uniform event framework and send the event structure to a set of event subscribers for consumption of the event structure. Each event publisher in the set of event publishers is further configured to receive different callbacks from different event subscribers in the set of event subscribers for different sets of data associated with the event.

Uniform event framework

Systems and methods of providing data change notifications using OData entity keys are disclosed. In some example embodiments, a first modification of a first property data of a first entity of a first entity type in a relational database is detected, with the first entity having at least one first OData key distinct from the first property data. In some example embodiments, a first event notification comprising a first indication that the first property data has been modified and the at least one first OData key is generated based on an event structure model in response to the detection of the first modification of the first property data, with the first event notification being absent the modified first property data, and the first event notification is transmitted to at least one API.

Data change notification using OData entity keys

An analytical request for information that includes queryable attributes mapped to corresponding fields of customer records from in-memory database of a number of data sources is received. Semantic mapping of the queryable attributes to the corresponding fields of the customer records is resolved according to semantic mapping metadata. A query that includes the corresponding fields is generated and over the in-memory database views and a number fan records each representing a unique fan entity. Fan related data is retrieved from the number of fan records and the in-memory database views based on the executed at least one query. Upon executing the query, at runtime the in-memory database views are dynamically integrated with the number fan records based on a cross-reference table linking the in-memory database views with the number of fan records based on a fan identifier.

Fan identity data integration and unification

Growing community of inventors

Cupertino, CA, United States of America

Baskaran Janarthanam