Salesforce Com, Inc.

Salesforce, Inc.

Nio Nextev Limited

Heng Zhang

Zhidong Ke

Utsavi Benani

Kevin Terusaki

Yifeng Liu

Priyadarshini Mitra

Jeffrey Dan Rupp

Yogesh Patel

Percy Dara Mehta

Mahalaxmi Sanathkumar

Christopher Eckert

Jayanth Parayil Kumarji

Aaron Zhang

Zhenyu Wang

Sreya Basuroy

Karthik Vijayan

Tongzhou Zhou

Yih-Charng Deng

Evan Jiang

Birva Joshi

Online meeting software typically generates a flow of data. A server system is configured to receive the flow of data, which may include metadata. The data may include metadata of online meetings. Different types of metadata are generated by online meetings. Such different types of metadata are provided in different patterns. Different types of metadata are provided throughout the online meeting session or at various points of the session and are provided to various different elements of the server system. The various different metadata received are then parsed and certain specific metadata elements are identified to match the different metadata streams.

Asynchronous online meeting metadata flow

Various techniques and mechanisms for sharing remote resources among a trusted group are disclosed. A credential management agent utilizes a resource credential for a first user to access a secure resource corresponding to the first user for a second user by at least validating a second user and validating a consent of the first user to allow the second user to access the secure resource using the resource credential for the first user. The secure resource resides on a remote server system accessible via one or more application program interfaces (APIs). A platform management agent provides an interface for shared resource-agnostic credential sharing. The platform management agent validates credentials for the second user as belonging to a trusted group and forwards a request for access to the secure resource for the second user to the credential management agent. In response to receiving the resource credential for the first user to access the secure resource, the platform management agent accesses the secure resource on behalf of the second user to allow the second user to utilize the secure resource.

Techniques and architectures for sharing remote resources among a trusted group of users

Mechanisms and techniques for providing an isolated runtime environment are disclosed. Scoped properties are generated utilizing a namespace identifier. The namespace identifier is an identifier used to define a scope of at least an isolated application runtime context. Scoped objects are generated corresponding to one or more dependent services utilizing the one or more scoped properties and the namespace identifier. A target application is deployed to a container corresponding to the isolated application runtime context. The target application interacts with at least some of the dependent services utilizing the namespace identifier. At least one integration test is run on the target application in the container. The integration tests refer to the isolated application runtime context utilizing the namespace identifier.

Techniques and architectures for providing an isolated runtime context in a shared environment

Techniques and mechanisms for ingesting data through an atomic transaction are disclosed. Raw data is received from multiple disparate sources to be consumed in an environment that does not support atomic write operations to data consumers. The environment has at least a data table and a notification table. A write to an entry in the data table having an associated version is attempted. The data table entry corresponds to the data to be consumed. A write to a corresponding entry to the notification table is attempted in response to a successful write attempt to the data table. The notification table entry includes information about the corresponding data table entry. The version associated with the data table is modified in response to successful writes of both the data table entry and the notification table entry. At least one data consumer is notified that the data table version has been modified.

Techniques and architectures for providing atomic transactions across multiple data sources

Managing mutations in a data lake environment. A mutation request to cause write operations that modify data objects or structures within an environment for collecting unformatted raw data is received. The environment has at least a data table and a notification table. An entry is written to the data table with a streaming job configured to receive and process the mutation request. Entries to the data table specify at least records indicating changes to objects in the environment based on ingestion processing for the environment for collecting unformatted raw data and based on the mutation request. A corresponding entry is written to the notification table in response to a successful write attempt to the data table. The notification table entry has information about data table entries for a specified period. At least one data consumer is notified that the data table has been modified.

Techniques and architectures for managing cascading mutations in an environment having a data lake

Mechanisms and techniques for providing continuous integration and continuous deployment (CI/CD) for data lake applications are disclosed. Assembly of code for an app is managed with a CI platform to create a container within a shared environment within which the app runs. The container is isolated from other containers and bundles software, libraries and configuration files and can communicate with other containers through defined channels. The shared environment provides a platform for running the app. The app writes to one or more tables maintained in the shared environment. Assembly of subsequent versions of code for the app is managed by the CI platform. Deployment of the assembled subsequent version of the code to the container is managed by the CI platform. Integration tests are run on the deployed subsequent version of the code with the CI platform. The subsequent version of the code replaces the app in the shared environment when integration testing is complete.

Techniques and architectures for providing continuous integration (CI) and/or continuous delivery (CD) in a data lake environment

A system and method of inflating an airbag and trajectory control tube are disclosed. The system and method include detecting application of a force at at least one of a plurality of sensors, initiating an inflation system to cause inflation of the airbag and the trajectory control tube responsive to the detecting, inflating the trajectory control tube based on the initiating, inflating the airbag, and breaching the airbag and the trajectory control tube compartment. The system and method include guiding the airbag deployment trajectory via the trajectory control tube guides the airbag deployment trajectory. The system and method include the guiding occurs as the airbag begins to inflate, as the airbag inflates, after the airbag has inflated or before the airbag inflates.

Airbag deployment trajectory control mechanism and method

Growing community of inventors

San Jose, CA, United States of America

Heng Zhang