Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: Described is a method and system for verifying the end-to-end distribution of messages within an on-demand services platform. To provide the ability to monitor and trace such messages, the system may include a specialized and queryable datastore (or database) that allows the system to track the distribution and acknowledgement of messages throughout the services platform. Accordingly, a specialized verification process may be initiated to query the database to verify the receipt of a message has been acknowledged by various components within the system. In addition, the verification process may automatically retry the distribution the messages to ensure particular downstream components have received the message. Accordingly, the system alleviates the need to manual re-crawl various message source to ensure the end-to-end distribution of such messages.

Abstract: 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.

Abstract: 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.

Abstract: Techniques and mechanisms to manage deletions from data tables are disclosed. A request to delete data from at least one data table in an environment having tables storing data from multiple disparate sources is received. The environment can also have a delete request status table and a notification table. Processing of the delete request is managed utilizing a multi-stage workflow where stages of the multistage workflow are tracked by updating entries to the delete request status table. Completion of the delete request is verified by checking at least one entry in the delete request status table corresponding to the delete request. A corresponding entry is written to the notification table in response to a successful verified completion of the delete request.

Abstract: 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.

Abstract: 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.

Abstract: Architectures and techniques to provide an extract-once framework for data ingestion into a data lake. A data consumption job to ingest data to multiple tables within a data collection platform is started. Checkpoint metadata corresponding to the data consumption job is retrieved from a checkpoint metadata store. A subset of processes from the data consumption job are performed. Checkpoint metadata is updated in response to completion of the subset of processes. A subsequent subset of processes from the data consumption job is performed. Checkpoint metadata is updated in response to completion of each of the at least one subsequent subset of processes from the data consumption job. Batch metadata is updated in response to completion of the data consumption job.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: Techniques and mechanisms for incremental data ingestion are disclosed. Raw data is received from multiple disparate sources to be consumed in an environment for collecting unformatted raw data. The environment has at least a delta data table and a delta notification table. A write to an entry in the delta data table is attempted. Entries to the delta data table specify at least records indicating changes to objects in the environment. A write a corresponding entry to the delta notification table is attempted in response to a successful write attempt to the delta data table. The delta notification table entry includes information about delta data table entries for a specified period. At least one data consumer is notified that the delta data table has been modified.

Abstract: Described is a method and system for verifying the end-to-end distribution of messages within an on-demand services platform. To provide the ability to monitor and trace such messages, the system may include a specialized and queryable datastore (or database) that allows the system to track the distribution and acknowledgement of messages throughout the services platform. Accordingly, a specialized verification process may be initiated to query the database to verify the receipt of a message has been acknowledged by various components within the system. In addition, the verification process may automatically retry the distribution the messages to ensure particular downstream components have received the message. Accordingly, the system alleviates the need to manual re-crawl various message source to ensure the end-to-end distribution of such messages.

Abstract: A system may identify gap events in a change detection stream. When changes in data are transmitted to a downstream system, the system may identify intermittent portions of the transmission where data is missing (e.g., a gap event). In some examples, a gap event may be caused by system maintenance or one or more system errors. After identifying the gap event, the system may bridge the gap event using metadata associated with the gap event. The associated metadata may be transmitted (e.g., via a gap event identification message) to the downstream system, which may prevent the downstream system from experiencing computational inefficiencies due to the gap event.

Abstract: A system may identify gap events in a change detection stream. When changes in data are transmitted to a downstream system, the system may identify intermittent portions of the transmission where data is missing (e.g., a gap event). In some examples, a gap event may be caused by system maintenance or one or more system errors. After identifying the gap event, the system may bridge the gap event using metadata associated with the gap event. The associated metadata may be transmitted (e.g., via a gap event identification message) to the downstream system, which may prevent the downstream system from experiencing computational inefficiencies due to the gap event.

Abstract: Secondary indexing mechanisms are disclosed. A first index is created in a database environment. The index has a scope defined by a set of files that meet a pre-selected criteria. Second index generation is initiated. Te second index has the same scope as the first index. A first time period between initiation of the generation of the second index and completion of the second index is determined. The second index is swapped with the first index in an atomic swap operation. The indices may be generated for a multitenant database environment. Catch up indexing may be performed for the secondary index.