Patent ID: 12248587

DETAILED DESCRIPTION

In some examples, a framework is provided having simple and easy interactions in addition to richer User Interface (UI) controls enabling users to build applications. The framework improves on traditional application development environments by providing a way to tie a security boundary of an application UI to a security boundary of data. In addition, there is no additional operational or management cost for running the applications as they are run within an existing environment and managed like any other workload.

In some examples, User Defined Function (UDF) server objects are created in a database, so they use the same permissions to be able to run them as other first-class objects within the database. They run in a security boundary the same as other stored procedures having owners' rights, so the permissions can be locked down to the role of the owner. An owner can set the permissions on the UDF server object itself, defining who can use it, as well as setting a different role for running it. When a server object is created, it becomes associated with a URL that can be hit by a Web Browser. When, the URL is hit, the system: 1) verifies their permissions against the UDF server object that is created; and 2) launches a special stored procedure that runs for an extended period of time in the security context that was configured on the UDF server; 3) the stored procedure creates a UDF Server that can securely run scripts in a locked down environment and a communication channel providing secure communications to the UDF server; and 4) The UDF Server runs a user defined web application using the communication channel to proxy communications from the browser to the web application in a low-latency and efficient way.

In some examples, a data platform for managing an application as a first-class database object includes at least one processor and a memory storing instructions that cause the at least one processor to perform operations including: detecting a data request from a browser for a data object located on the data platform; executing a stored procedure, the stored procedure containing instructions that cause the at least one processor to perform additional operations including: instantiating a User Defined Function (UDF) server, an application engine, and the application within a security context of the data platform based on a security policy determined by an owner of the data object. The data platform then communicates with the browser using the application engine as a proxy server.

In some examples, the stored procedure comprises the application engine.

In some examples, the browser includes an application browser runtime component for communicating with the application. In some examples, the security policy includes a security manager policy. In some examples, the instructions cause the at least one processor to perform operations including receiving a request from the browser for access to the data object, and verifying, by a sandbox process, the access to the data object based on a sandbox policy.

In some examples, the instructions cause at least one processor to perform operations including receiving a request from the browser for access to the data object, verifying the request based on defined security policies and executing instructions in a sandbox process to restrict access beyond what the data object is permitted to access.

Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.

The data platform may also include where the instructions that cause the at least one processor to perform operations of instantiating a User Defined Function (UDF) server within a security context of the data platform further cause the at least one processor to perform operations includes verifying, by a security manager, the UDF server based on the security manager policy. Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.

Reference will now be made in detail to specific examples for carrying out the inventive subject matter. Examples of these specific examples are illustrated in the accompanying drawings, and specific details are set forth in the following description in order to provide a thorough understanding of the subject matter. It will be understood that these examples are not intended to limit the scope of the claims to the illustrated examples. On the contrary, they are intended to cover such alternatives, modifications, and equivalents as may be included within the scope of the disclosure.

FIG.1illustrates an example computing environment100that includes a data platform102in communication with a client device112, in accordance with some examples of the present disclosure. To avoid obscuring the inventive subject matter with unnecessary detail, various functional components that are not germane to conveying an understanding of the inventive subject matter have been omitted fromFIG.1. However, a skilled artisan will readily recognize that various additional functional components may be included as part of the computing environment100to facilitate additional functionality that is not specifically described herein.

As shown, the data platform102comprises a database storage106, a compute service manager104, an execution platform110, and a metadata database114. The database storage106comprises a plurality of computing machines and provides on-demand computer system resources such as data storage and computing power to the data platform102. As shown, the database storage106comprises multiple data storage devices, namely data storage device1108ato data storage device N108d. In some examples, the data storage devices1to N are cloud-based storage devices located in one or more geographic locations. For example, the data storage devices1to N may be part of a public cloud infrastructure or a private cloud infrastructure. The data storage devices1to N may be hard disk drives (HDDs), solid state drives (SSDs), storage clusters, Amazon S3™ storage systems or any other data storage technology. Additionally, the database storage106may include distributed file systems (e.g., Hadoop Distributed File Systems (HDFS)), object storage systems, and the like.

The data platform102is used for reporting and analysis of integrated data from one or more disparate sources including the storage devices1to N within the database storage106. The data platform102hosts and provides data reporting and analysis services to multiple customer accounts. Administrative users can create and manage identities (e.g., users, roles, and groups) and use permissions to allow or deny access to the identities to resources and services. Generally, the data platform102maintains numerous customer accounts for numerous respective customers. The data platform102maintains each customer account in one or more storage devices of the database storage106. Moreover, the data platform102may maintain metadata associated with the customer accounts in the metadata database114. Each customer account includes multiple data objects with examples including users, roles, permissions, stages, and the like.

The compute service manager104coordinates and manages operations of the data platform102. The compute service manager104also performs query optimization and compilation as well as managing clusters of compute services that provide compute resources (also referred to as “virtual warehouses”). The compute service manager104can support any number and type of clients such as end users providing data storage and retrieval requests, system administrators managing the systems and methods described herein, and other components/devices that interact with compute service manager104. As an example, the compute service manager104is in communication with the client device112. The client device112can be used by a user of one of the multiple customer accounts supported by the data platform102to interact with and utilize the functionality of the data platform102.

The compute service manager104is also coupled to metadata database114. The metadata database114stores data pertaining to various functions and aspects associated with the data platform102and its users. In some examples, the metadata database114includes a summary of data stored in remote data storage systems as well as data available from a local cache. Additionally, the metadata database114may include information regarding how data is organized in remote data storage systems (e.g., the database storage106) and the local caches. The metadata database114allows systems and services to determine whether a piece of data needs to be accessed without loading or accessing the actual data from a storage device.

The compute service manager104is further coupled to the execution platform110, which provides multiple computing resources that execute various data storage and data retrieval tasks. In some examples, the compute service manager104communicates with the execution platform110concerning jobs and tasks using a queue within the data platform102. This isolates the operations of the execution platform110and the client device112. The execution platform110is coupled to the database storage106. The execution platform110comprises a plurality of compute nodes. A set of processes on a compute node executes a query plan compiled by the compute service manager104. The set of processes can include: a first process to execute the query plan; a second process to monitor and delete micro-partition files using a least recently used (LRU) policy and implement an out of memory (OOM) error mitigation process; a third process that extracts health information from process logs and status to send back to the compute service manager104; a fourth process to establish communication with the compute service manager104after a system boot; and a fifth process to handle all communication with a compute cluster for a given job provided by the compute service manager104and to communicate information back to the compute service manager104and other compute nodes of the execution platform110.

In some examples, communication links between elements of the computing environment100are implemented via one or more data communication networks. These data communication networks may utilize any communication protocol and any type of communication medium. In some examples, the data communication networks are a combination of two or more data communication networks (or sub-networks) coupled to one another. In alternate examples, these communication links are implemented using any type of communication medium and any communication protocol.

As shown inFIG.1, the data storage devices data storage device1108ato data storage device N108dare decoupled from the computing resources associated with the execution platform110. This architecture supports dynamic changes to the data platform102based on the changing data storage/retrieval needs as well as the changing needs of the users and systems. The support of dynamic changes allows the data platform102to scale quickly in response to changing demands on the systems and components within the data platform102. The decoupling of the computing resources from the data storage devices supports the storage of large amounts of data without requiring a corresponding large amount of computing resources. Similarly, this decoupling of resources supports a significant increase in the computing resources utilized at a particular time without requiring a corresponding increase in the available data storage resources.

The compute service manager104, metadata database114, execution platform110, and database storage106are shown inFIG.1as individual discrete components. However, each of the compute service manager104, metadata database114, execution platform110, and database storage106may be implemented as a distributed system (e.g., distributed across multiple systems/platforms at multiple geographic locations). Additionally, each of the compute service manager104, metadata database114, execution platform110, and database storage106can be scaled up or down (independently of one another) depending on changes to the requests received and the changing needs of the data platform102. Thus, in the described examples, the data platform102is dynamic and supports regular changes to meet the current data processing needs.

During operation, the data platform102processes multiple jobs determined by the compute service manager104. These jobs are scheduled and managed by the compute service manager104to determine when and how to execute the job. For example, the compute service manager104may divide the job into multiple discrete tasks and may determine what data is needed to execute each of the multiple discrete tasks. The compute service manager104may assign each of the multiple discrete tasks to one or more nodes of the execution platform110to process the task. The compute service manager104may determine what data is needed to process a task and further determine which nodes within the execution platform110are best suited to process the task. Some nodes may have already cached the data needed to process the task and, therefore, be a good candidate for processing the task. Metadata stored in the metadata database114the compute service manager104in determining which nodes in the execution platform110have already cached at least a portion of the data needed to process the task. One or more nodes in the execution platform110process the task using data cached by the nodes and, if necessary, data retrieved from the database storage106. It is desirable to retrieve as much data as possible from caches within the execution platform110because the retrieval speed is typically faster than retrieving data from the database storage106.

As shown inFIG.1, the computing environment100separates the execution platform110from the database storage106. In this arrangement, the processing resources and cache resources in the execution platform110operate independently of the database storage devices data storage device1108ato data storage device N108din the database storage106. Thus, the computing resources and cache resources are not restricted to a specific of the data storage device1108ato data storage device N108d. Instead, all computing resources and all cache resources may retrieve data from, and store data to, any of the data storage resources in the database storage106.

FIG.2is a block diagram illustrating components of the compute service manager104, in accordance with some examples of the present disclosure. As shown inFIG.2, the compute service manager104includes an access manager202and a key manager204coupled to a data storage device206. Access manager202handles authentication and authorization tasks for the systems described herein. Key manager204manages storage and authentication of keys used during authentication and authorization tasks. For example, access manager202and key manager204manage the keys used to access data stored in remote storage devices (e.g., data storage devices in database storage106). As used herein, the remote storage devices may also be referred to as “persistent storage devices” or “shared storage devices.”

A request processing service208manages received data storage requests and data retrieval requests (e.g., jobs to be performed on database data). For example, the request processing service208may determine the data necessary to process a received query (e.g., a data storage request or data retrieval request). The data may be stored in a cache within the execution platform110or in a data storage device in database storage106.

A management console service210supports access to various systems and processes by administrators and other system managers. Additionally, the management console service210may receive a request to execute a job and monitor the workload on the system.

The compute service manager104also includes a job compiler212, a job optimizer214, and a job executor216. The job compiler212parses a job into multiple discrete tasks and generates the execution code for each of the multiple discrete tasks. The job optimizer214determines the best method to execute the multiple discrete tasks based on the data that needs to be processed. The job optimizer214also handles various data pruning operations and other data optimization techniques to improve the speed and efficiency of executing the job. The job executor216executes the execution code for jobs received from a queue or determined by the compute service manager104.

A job scheduler and coordinator218sends received jobs to the appropriate services or systems for compilation, optimization, and dispatch to the execution platform110. For example, jobs may be prioritized and processed in that prioritized order. In an example, the job scheduler and coordinator218determines a priority for internal jobs that are scheduled by the compute service manager104with other “outside” jobs such as user queries that may be scheduled by other systems in the database but may utilize the same processing resources in the execution platform110. In some examples, the job scheduler and coordinator218identifies or assigns particular nodes in the execution platform110to process particular tasks. A virtual warehouse manager220manages the operation of multiple virtual warehouses implemented in the execution platform110. As discussed below, each virtual warehouse includes multiple execution nodes that each include a cache and a processor.

Additionally, the compute service manager104includes a configuration and metadata manager222, which manages the information related to the data stored in the remote data storage devices and in the local caches (e.g., the caches in execution platform110). The configuration and metadata manager222uses the metadata to determine which data micro-partitions need to be accessed to retrieve data for processing a particular task or job. A monitor and workload analyzer224oversees processes performed by the compute service manager104and manages the distribution of tasks (e.g., workload) across the virtual warehouses and execution nodes in the execution platform110. The monitor and workload analyzer224also redistributes tasks, as needed, based on changing workloads throughout the data platform102and may further redistribute tasks based on a user (e.g., “external”) query workload that may also be processed by the execution platform110. The configuration and metadata manager222and the monitor and workload analyzer224are coupled to a data storage device226. Data storage device226inFIG.2represents any data storage device within the data platform102. For example, data storage device226may represent caches in execution platform110, storage devices in database storage106, or any other storage device.

As shown, the compute service manager104further includes an account replication manager228. The account replication manager228is responsible for handling account replication including automatic replication of security features.

The compute service manager104validates all communication from an execution platform (e.g., the execution platform110) to validate that the content and context of that communication are consistent with the task(s) known to be assigned to the execution platform. For example, an instance of the execution platform executing a query A should not be allowed to request access to data-source D (e.g., data storage device226) that is not relevant to query A. Similarly, a given execution node (e.g., execution node1304a) may need to communicate with another execution node (e.g., execution node2304b), and should be disallowed from communicating with a third execution node (e.g., execution node1316a) and any such illicit communication can be recorded (e.g., in a log or other location). Also, the information stored on a given execution node is restricted to data relevant to the current query and any other data is unusable, rendered so by destruction or encryption where the key is unavailable.

FIG.3is a block diagram illustrating components of the execution platform110, in accordance with some examples of the present disclosure. As shown inFIG.3, the execution platform110includes multiple virtual warehouses, including virtual warehouse1302a, and virtual warehouse2302bto virtual warehouse N302c. Each virtual warehouse includes multiple execution nodes that each includes a data cache and a processor. The virtual warehouses can execute multiple tasks in parallel by using the multiple execution nodes. As discussed herein, the execution platform110can add new virtual warehouses and drop existing virtual warehouses in real time based on the current processing needs of the systems and users. This flexibility allows the execution platform110to quickly deploy large amounts of computing resources when needed without being forced to continue paying for those computing resources when they are no longer needed. All virtual warehouses can access data from any data storage device (e.g., any storage device in database storage106).

Although each virtual warehouse shown inFIG.3includes three execution nodes, a particular virtual warehouse may include any number of execution nodes. Further, the number of execution nodes in a virtual warehouse is dynamic, such that new execution nodes are created when additional demand is present, and existing execution nodes are deleted when they are no longer necessary.

Each virtual warehouse is capable of accessing any of the data storage devices1to N shown inFIG.1. Thus, the virtual warehouses are not necessarily assigned to a specific data storage device1to N and, instead, can access data from any of the data storage devices1to N within the database storage106. Similarly, each of the execution nodes shown inFIG.3can access data from any of the data storage devices1to N. In some examples, a particular virtual warehouse or a particular execution node may be temporarily assigned to a specific data storage device, but the virtual warehouse or execution node may later access data from any other data storage device.

In the example ofFIG.3, virtual warehouse1302aincludes a plurality of execution nodes as exemplified by execution node1304a, execution node2304b, and execution node N304c. Execution node1304aincludes cache1306aand a processor1308a. Execution node2304bincludes cache2306band processor2308b. Execution node N304cincludes cache N306cand processor N308c. Each execution node1to N is associated with processing one or more data storage and/or data retrieval tasks. For example, a virtual warehouse may handle data storage and data retrieval tasks associated with an internal service, such as a clustering service, a materialized view refresh service, a file compaction service, a storage procedure service, or a file upgrade service. In other implementations, a particular virtual warehouse may handle data storage and data retrieval tasks associated with a particular data storage system or a particular category of data.

Similar to virtual warehouse1302adiscussed above, virtual warehouse2302bincludes a plurality of execution nodes as exemplified by execution node1310a, execution node2310b, and execution node N310c. Execution node1310aincludes cache1312aand processor1314a. Execution node2310bincludes cache2312band processor2314b, Execution node N310cincludes cache N312cand processor N314c. Additionally, virtual warehouse N302cincludes a plurality of execution nodes as exemplified by execution node1316a, execution node2316b, and execution node N316c. Execution node1316aincludes cache1318aand processor1320a. Execution node2316bincludes cache2318band processor2320b. Execution node N316cincludes cache N318cand processor N320c.

In some examples, the execution nodes shown inFIG.3are stateless with respect to the data the execution nodes are caching. For example, these execution nodes do not store or otherwise maintain state information about the execution node or the data being cached by a particular execution node. Thus, in the event of an execution node failure, the failed node can be transparently replaced by another node. Since there is no state information associated with the failed execution node, the new (replacement) execution node can easily replace the failed node without concern for recreating a particular state.

Although the execution nodes shown inFIG.3each includes one data cache and one processor, alternate examples may include execution nodes containing any number of processors and any number of caches. Additionally, the caches may vary in size among the different execution nodes. The caches shown inFIG.3store, in the local execution node, data that was retrieved from one or more data storage devices in database storage106. Thus, the caches reduce or eliminate the bottleneck problems occurring in platforms that consistently retrieve data from remote storage systems. Instead of repeatedly accessing data from the remote storage devices, the systems and methods described herein access data from the caches in the execution nodes, which is significantly faster and avoids the bottleneck problem discussed above. In some examples, the caches are implemented using high-speed memory devices that provide fast access to the cached data. Each cache can store data from any of the storage devices in the database storage106.

Further, the cache resources and computing resources may vary between different execution nodes. For example, one execution node may contain significant computing resources and minimal cache resources, making the execution node useful for tasks that require significant computing resources. Another execution node may contain significant cache resources and minimal computing resources, making this execution node useful for tasks that require caching of large amounts of data. Yet another execution node may contain cache resources providing faster input-output operations, useful for tasks that require fast scanning of large amounts of data. In some examples, the cache resources and computing resources associated with a particular execution node are determined when the execution node is created, based on the expected tasks to be performed by the execution node.

Additionally, the cache resources and computing resources associated with a particular execution node may change over time based on changing tasks performed by the execution node. For example, an execution node may be assigned more processing resources if the tasks performed by the execution node become more processor intensive. Similarly, an execution node may be assigned more cache resources if the tasks performed by the execution node require a larger cache capacity.

Although virtual warehouses1,2, and N are associated with the same execution platform110, the virtual warehouses may be implemented using multiple computing systems at multiple geographic locations. For example, virtual warehouse1can be implemented by a computing system at a first geographic location, while virtual warehouses2and N are implemented by another computing system at a second geographic location. In some examples, these different computing systems are cloud-based computing systems maintained by one or more different entities.

Additionally, each virtual warehouse as shown inFIG.3has multiple execution nodes. The multiple execution nodes associated with each virtual warehouse may be implemented using multiple computing systems at multiple geographic locations. For example, an instance of virtual warehouse1302aimplements execution node1304aand execution node2304bon one computing platform at a geographic location and implements execution node N304cat a different computing platform at another geographic location. Selecting particular computing systems to implement an execution node may depend on various factors, such as the level of resources needed for a particular execution node (e.g., processing resource requirements and cache requirements), the resources available at particular computing systems, communication capabilities of networks within a geographic location or between geographic locations, and which computing systems are already implementing other execution nodes in the virtual warehouse.

A particular execution platform110may include any number of virtual warehouses. Additionally, the number of virtual warehouses in a particular execution platform is dynamic, such that new virtual warehouses are created when additional processing and/or caching resources are needed. Similarly, existing virtual warehouses may be deleted when the resources associated with the virtual warehouse are no longer necessary.

In some examples, the virtual warehouses may operate on the same data in database storage106, but each virtual warehouse has its own execution nodes with independent processing and caching resources. This configuration allows requests on different virtual warehouses to be processed independently and with no interference between the requests. This independent processing, combined with the ability to dynamically add and remove virtual warehouses, supports the addition of new processing capacity for new users without impacting the performance observed by the existing users.

FIG.4Ais a deployment diagram of a computing environment400for providing a web application as a first-class database object in accordance with some examples. A data platform102utilizes the computing environment400to provide a secure framework for a user application410to be executed by an execution platform110of the data platform102. The user application410and all of the components supporting the user application410, such as, but not limited to, a Web application engine408and a User Defined Function (UDF) server406, collectively referred to as a “web application” herein, are treated by the data platform102as first-class database objects in that can be instantiated using one or more commands within a database query as illustrated by the code fragments.

To Create a New Web Application

CREATE [ OR REPLACE ] WEBAPP [ IF NOT EXISTS ] <Webapp_name>[ VERSIONS ] (versionList)[ WAREHOUSE = <warehouse_name> ][ COMMENT = ‘<comment_string_literal>’ ]versionList : = versionInfo [, versionInfo ]id = <webapp_version_name>root_location = <app_root>file_path = <file_name>
To Drop a Web Application:DROP WEBAPP[ IF EXISTS]<webapp_name>
To Alter an Existing Web Application

ALTER WEBAPP [IF EXISTS] <webapp_name> SET[ WAREHOUSE = < warehouse_name> ][ DEFAULT_VERSION = <webapp_version_name> ][ COMMENT = ‘<string_literal>’ ]ALTER WEBAPP [IF EXISTS] <webapp_name>ADD [(] versionList [)]ALTER WEBAPP [IF EXISTS] <webapp_name>DROP [(]<webapp_version_name> [,<webapp_version_name>...][)]ALTER WEBAPP [IF EXISTS] <webapp_name> MODIFY[(] modifyWebappVersionList [)]modifyWebappVersionList :=modifyWebappVersionAttr, [, modifyWebappVersionAttr]modifyWebappVersionAttr := [VERSION] <webapp_version_name>SET { root_location = <app_root> | file_path = <file_name> }
Where:<Webapp_name>Specifies the identifier for the web application, unique for the schema it is created in.<webapp_version name>Specifies the identifier for the version of the web application.<app_root>A reference to a stage URL that points to a root of the user application410. When the user application runs, the files below this app_root will be available to the web application engine408. Although versions can be in the same stage or data location within the data platform102, separated only by prefixes it can be useful to have different stages per-version to manage permissions and cleanup better.<file_name>A path to a user file to run as part of the web application engine408. This is relative to the <app_root>.<warehouse_name>A name of a virtual warehouse, such as virtual warehouse1302aof the data platform102to run the user application410.<comment_string literal>Comment describing the web user application410.

A partial list of permissions enforced by the security manager policy420and/or the sandbox policy422for the user application410and its supporting components are described in Table 1 and Table 2:

TABLE 1PrivilegeUsageCREATE WEBAPPThe ability to create a user application 410and its associated components in a schema.

TABLE 2PrivilegeUsageUSAGEEnables hitting the HTTPS endpoint forthe user application 410 on the defaultversion. Enables seeing the webapplication using DESCRIBE orSHOW commandsALL [PRIVILEGES]Grant all privileges other than OWNERSHIPOWNERSHIPGrants full control over the webapplication; required to drop the userapplication 410. Only a single role can holdthis privilege on a specific object at atime

In some examples, there are objects of the data platform102that the user application410depends on, such as, but not limited to, a storage location or stage for storing files, and a virtual warehouse, such as virtual warehouse1302a, within which the user application410is loaded. When creating a user application410and its associated components that reference a stage, the user application410inherits READ permissions to that stage and USAGE permissions to the virtual warehouse.

In some examples, the web application has direct access to source files that define the operations of the web application, but a user of the web application does not have the same permissions to access the source files. The web application accesses the source files via the stage.

In some examples, if a stage's permissions are changed after a user application410is created, such that the owner of the user application410no longer has permissions to it, then requests to the user application410will fail with an error stating that the user application410does not exist. If a Warehouse's permissions are changed after the user application410is created, then the logic for the warehouse to use will act as if no warehouse was set.

In some examples, a stage or data location is embedded in the user application410or one of its associated components and the permissions to the user application410and the permissions of the stage are associated together. In some examples, a user application410and its related components may be shared with other owners or users in accordance with permissions stored in the security manager policy420and/or sandbox policy422.

Accordingly, when instantiated, the user application410and all of its supporting components inherit all of the attributes of a first-class object within a database provided by the data platform102including permissions and restrictions that may be utilized by the data platform102to manage a database object. In some examples, the user application410is provided as a service by the UDF server406utilizing the web application engine408and can be accessed over a network, such as the Internet, by a web application browser runtime component404included in a browser402hosted by a client device112utilizing protocols that are used to access documents and files on the World Wide Web.

As described in reference toFIG.2, the compute service manager104implements security protocols that validate all communication from the execution platform110to validate that the content and context of that communication are consistent with the task(s) known to be assigned to the execution platform110. For example, the execution platform110executing a query A is not allowed to request access to a particular data source (e.g., data storage device226or any one of the storage devices in the database storage106) that is not relevant to query A. In an example, an execution node424may need to communicate with a second execution node but the security mechanisms described herein can disallow communication with a third execution node. Moreover, any such illicit communication can be recorded (e.g., in a log418or other location). Further, the information stored on a given execution node is restricted to data relevant to the current query and any other data is unusable by destruction or encryption where the key is unavailable.

In some examples, the UDF server406and its components, such as the web application engine408and the user application410are implemented in a particular programming language such as Python, and the like. In some examples, the web application browser runtime component404is implemented in a different programming language (e.g., C or C++) than the UDF server406, which can further improve security of the computing environment400by using a different codebase (e.g., one without the same or fewer potential security exploits).

The UDF server406receives communications from the web application browser runtime component404the global service process444of the data platform102. The global service process444is responsible for receiving requests from the web application browser runtime component404. The global service process444uses components of the compute service manager104to perform various authentication tasks including a first level of authorization using an access manager202of the compute service manager104. The UDF server406performs tasks including assigning processing threads to execute user code of the user application410and returning the results generated by the user application410to the web application browser runtime component404via the global service process444.

In some examples, the UDF server406executes within a sandbox process414as more fully described below. In some embodiments, the UDF server406is implemented in Python interpreted by an interpreter process. In some examples, the UDF server406is implemented in another language, such as Java, executed by a virtual machine (JVM). Since the UDF server406advantageously executes in a separate process relative to the browser402, there is a lower risk of malicious manipulation of the user application410.

Results of performing an operation, among other types of information or messages, can be stored in a log418for review and retrieval. In an embodiment, the log418can be stored locally in memory at the execution node424, or at a separate location such as the database storage106.

In some examples, a security manager416, can prevent completion of an operation from a user application410by throwing an exception (e.g., if the operation is not permitted), or returns (e.g., doing nothing) if the operation is permitted. In an implementation, the security manager416is implemented as a security manager object that allows an application to implement a security policy such as a security manager policy420and enables the application to determine, before performing a possibly unsafe or sensitive operation, what the operation is and whether it is being attempted in a security context that allows the operation to be performed. The security manager policy420can be implemented as a file with permissions that the UDF server406is granted. The UDF server406therefore can allow or disallow the operation based at least in part on the security policy.

In some embodiments, the sandbox process414reduces the risk of security breaches by restricting the running environment of untrusted applications using security mechanisms such as namespaces and secure computing modes (e.g., using a system call filter to an executing process and all its descendants, thus reducing the attack surface of the kernel of a given operating system). Moreover, in an example, the sandbox process414is a lightweight process and is optimized (e.g., closely coupled to security mechanisms of a given operating system kernel) to process a database query or other service request in a secure manner within the sandbox environment.

In some examples, the sandbox process414can utilize a virtual network connection in order to communicate with other components within the computing environment400. A specific set of rules can be configured for the virtual network connection with respect to other components of the computing environment400. For example, such rules for the virtual network connection can be configured for a particular UDF server406to restrict the locations (e.g., particular sites on the Internet or components that the UDF server406can communicate) that are accessible by operations performed by the UDF server406. Thus, in this example, the UDF server406can be denied access to particular network locations or sites on the Internet.

The sandbox process414can be understood as providing a constrained computing environment for a process (or processes) within the sandbox, where these constrained processes can be controlled and restricted to limit access to certain computing resources.

Examples of security mechanisms can include the implementation of namespaces in which each respective group of processes executing within the sandbox environment has access to respective computing resources (e.g., process IDs, hostnames, user IDs, file names, names associated with network access, and inter-process communication) that are not accessible to another group of processes (which may have access to a different group of resources not accessible by the former group of processes), other container implementations, and the like. By having the sandbox process414execute as a sub-process, in some examples, latency in processing a given database query can be substantially reduced in comparison with other techniques that may utilize a virtual machine solution by itself.

As further illustrated, the sandbox process414can utilize a sandbox policy422to enforce a given security policy. The sandbox policy422can be a file with information related to a configuration of the sandbox process414and details regarding restrictions, if any, and permissions for accessing and utilizing system resources. Example restrictions can include restrictions to network access, or file system access (e.g., remapping file system to place files in different locations that may not be accessible, other files can be mounted in different locations, and the like). The sandbox process414restricts the memory and processor (e.g., CPU) usage of the UDF server406, ensuring that other operations on the same execution node can execute without running out of resources.

The web application browser runtime component404provides a frontend for the user application410. The web application browser runtime component404performs browser interactions with the data platform102for the user application410. Components of the computing environment400communicate using a communication channel412that provides a set of commands that are used for interactions between the user application410and the browser402. The communication channel412logically interacts with the user application410, and physically goes through the layers of the data platform102to ensure security restrictions and policies are enforced at each layer. These may include permissions or runtime requirements from the compute service manager104.

The web application browser runtime component404sends back messages that are processed by the execution platform110and responded to with a series of forward messages.

The web application engine408includes instructions that can be defined by third parties but are run as an application within the execution platform110. The web application engine408provides programming frameworks that users can build applications, such as the user application410. In some examples, the web application engine408is written in Python and is treated by the execution platform110as special Python stored procedures. In some examples, the web application engine408is written in another language, such as, but not limited to Java, and hosted by a virtual machine within the execution platform110. In some examples, third parties may build their own web application engines.

The user application410comprises an application written by an end user and evaluated by the web application engine408. In some examples, the user application410comprises Python files that are evaluated by a proprietary Python interpreter.

The UDF server406is in charge of running UDFs in a controlled execution environment such as the sandbox process414. In some examples, the UDF server406comprises a Python UDF server. In some examples, the UDF server406utilizes other languages, such as Java.

In some examples, a Uniform Resource Locator (URL) identification of an assigned to the UDF server406is a unique value that is stable across replications of the UDF server406. For example, the URL identification is a randomly generated string that is unique within an account of an owner. The URL identification may be created by using a UUID4 and Base64 encoding to give it a more concise representation.

In some examples, a schema object of the data platform102is used to define the components of the web application such as, but not limited to, the UDF server406, the web application engine408, the user application410, and the web application browser runtime component404. The name, network endpoint, permissions and policies are based on this object. In some examples, the schema object includes a particular version of a web application engine408to use as well as any resource constraints.

In some examples, version of a user's code is specified and will associate a named version of a web application that refers to a place on a storage location or stage used by the data platform102to run user code.

FIG.4B,FIG.4C, andFIG.4Dare interaction and data flow diagrams of the computing environment400for providing a web application as a first-class database object in accordance with some examples.

The computing environment400utilizes Row Set Operators (RSOs) that run as part of a program in the execution platform110. An RSOI is an instance of an RSO that operates on a processing thread of the execution platform110. An RSOI extension function is an RSOI that runs stored procedures. In some examples, the stored procedures are written in Python. In some examples, the stored procedures are written in Java.

The owner role of the database object defines how metadata such as permissions are stored. Permissions are set on the database object define the security can use the RSOI extension function436, and which role it runs as. Setting these permissions happens when a user defines the database object, and enforcement happens in the web application resource442when the browser accesses a URL associated with the web application, and through the role used to run RSOI extension function436. The web application resource442will also start the job, which sets its permissions context. The RSOI extension function436operates within that permissions/session context.

In some examples, an owner sets permissions on each of the objects that will be instantiated such as, but not limited to, a UDF server406, a web application engine408, and a user application410.

In some examples, various HTTP responses are set to govern whether the browser security policies are enforced based on permissions defined in the security manager policy420.

In operation1, a user uses the browser402to communicate a request to the data platform102for data of a database object of the data platform102. The browser402hosted by client device112uses a Web socket connection to a web application resource442to communicate with user application410hosted by the data platform102that will access the database object. When the web application resource442detects that the browser402is making the request, the access manager202of the compute service manager104of the data platform102authorizes access to the user application410based on a set of security policies stored on data storage device206.

The web application browser runtime component404pulls back messages off the web socket and issues appropriate commands. If there is no current session having an instance of the web application engine408, the web application browser runtime component404verifies the request has permissions to use the user application410based on the security manager policy420, then requests start of a job by the UDF server406. An initial execution plan starts an instance of a web application engine408for the job using a security context of the user application410. The web application engine408will be instantiated based on the security manager policy420and the sandbox policy422enforced respectively by the security manager416and the sandbox process414, and the event is logged into the log418. After there is a session of the web application engine408started, the web application engine408sends commands to a query coordinator430.

In operation2, the job has the query coordinator430associated with the job. From this point on, communication to the web application engine408occurs by adding query coordinator events of type “application interaction” to the query coordinator430. This results in a run request being enqueued. The query coordinator event also has a reference to a stream it can send forward messages through to get to the browser402. That way the query coordinator430can get the response events and pass them directly back to the browser402.

In operation3, an application request queue426is provided. The application request queue426is an in-memory queue that back messages are pushed onto. In some examples, the application request queue426is in memory to ensure the connection at operation4always goes back to the same global service instance as the query coordinator430is on. In some examples, in the case of a global service failure, it is permissible to lose the messages and have the web application browser runtime component404re-establish the state through a new run request.

In operation4, an RSOI extension function436launches a special stored procedure that runs for a long time. This stored procedure runs in the security context that was configured for the objects that will be instantiated on the execution node424based on the security manager policy420and the sandbox policy422. The stored procedure creates a UDF server406that securely runs scripts in the locked down environment of the execution node424of the execution platform110. The RSOI extension function436starts the web application engine408based on the stored procedure through the UDF server406using RPC calls. The RSOI extension function436calls an “execute procedure” with function information that will tell the stored procedure of the web application engine408not to terminate. The web application engine408is instantiated based on the security manager policy420and the sandbox policy422enforced, respectively, by the security manager416and the sandbox process414during a verification process, and the event is logged into the log418. The procedure of the web application engine408connects to a stream application requests RPC endpoint on the UDF server406and issues an initialize application message. That message will be used to bootstrap the web application engine408with the appropriate policy and file information to run the user application410. This information comes down as part of the execution plan of operation1that starts the user application410. The RSOI extension function436connects to a web application interaction channel434endpoint in an execution platform resource432, and processes messages that come in through that channel. The UDF server406is then able to run the web application engine408and the user application410using the special stored procedure to proxy communications from the browser in a low-latency and efficient way.

In some examples, network endpoints are determined based on the account locator based URLs, thus providing a domain for owner's account and each web application associated with the owner's account to act as a browser security boundary. In additional examples, components of an URL identifier are unique, an unguessable numbers. The URL identifications are stable across renames and replication to other accounts. A user of the browser402may access the URL directly. To do so, they will be required to be logged in to the data platform102, and they will need usage privileges on the user application410.

The messages coming from the execution platform resource432are user driven interactions that come from either using or editing an application. The messages that go to the UDF server406are defined in a document that defines the UDF application requests. For application user requests, the RSOI extension function436: 1. Acts as a proxy server and communicates back message requests to an appropriate UDF server406, and leaves them to be processed by the web application engine408; 2. Receives an update file message request that commands the RSOI extension function436to: a. Find files that need to be updated; b. Issue an update file start command; c. Follow with the update file commands needed to update the appropriate files used by the web application engine408; and d. Generate an update files end message.

All access to the execution platform110such as, but not limited to, data stored in the database storage106and additional functions and procedures executed by the execution platform110, by the user application410using the web application engine408is verified by the security manager416and the sandbox process414using the security manager policy420and the sandbox policy422, respectively. This allows the execution platform110to provide services to the browser402by the user application410without requiring the data to move between a secured location and an unsecured location with the execution platform110, thus enhancing scalability and security. In some examples, for the HTTP channel for an “execution platform resource” command, ContentType=application/octet-stream is used, with the Protobuf protocol being used in both directions. In some examples, the Protobuf protocol is used in both directions in a coded fashion that will allow pushing multiple messages down a stream without having to close the TCP connection and re-issue a request.

In operation5, in reference toFIG.4D, the UDF server406manages the lifecycle of the web application engine408. The UDF server406launches and then manages requests that come in through a stream application requests endpoint. With reference toFIG.4D, in some examples, there are two basic types of messages: application user requests440and application control plane requests438. Application user requests440get passed directly into a run method for the web application engine408. Application control plane requests438are directed to the UDF server406to do some system operation, such as but not limited to, updating files, initializing applications or shutting things down.

In operation6, a web application procedure includes additional lifecycle functions that get called. An example web application procedure is partially illustrated in the code fragment:

// Called when InitializeApp message comes indef start (webApp: WebApp, config: ConfigurationParameters)// Main function for processing app requests.// Called for each BackMsg that comes indef run(webApp: WebApp, message: BackMsg, responseQueuequeue<ForwardMsg>, sessionCtx: SessionCtx)// Called when the files are updateddef beforeFilesChanged (webApp: WebApp, files: List<Files>)def afterFilesChanged (webApp: WebApp, files: List<Files>)// Called before the app endsdef stop (webApp: WebApp)

In some examples, the UDF server406knows what functions associate with which operations by being specified in a stored procedure Data Persistence Object (DPO) passed down as part of starting the web application engine408. In some examples, the UDF server406knows what functions associate with which operations as a stored procedure DPO has a handler as a start function, and a return type of the start function returns a table of functions that specifies other functions. In some examples, the UDF server406knows what functions associate with which operations as a stored procedure DPO has a handler as the start function, and annotations are provided that the UDF server406can look for to find other functions. In some examples, a new property on a stored procedure marks the stored procedure as a web application engine408. When this is set, a handler calls a function that returns a table of the functions that map to the different application lifecycle events above (e.g., run, files changed, etc.)

In operation7, responses from the UDF server406come back through an execution platform resource. When the user application410adds messages to an application response queue428, the UDF server406will take those responses and pass them back through the RPC endpoint to the RSOI extension function436, which will then send them down a long-poll HTTP connection to the web-app-interaction-channel in the execution platform resource. The execution platform resource puts the responses in the application response queue428and notifies the query coordinator430.

In operation8, the query coordinator430sends the response back to the browser402. The query coordinator430picks up the events, filters out any messages that violate policy (e.g. unrestricted JS or HTML). As the query coordinator430was already provided with the response channel when it got the query coordinator event, so it uses this to send back a response. In some examples, when it is assured that the web socket is in a same global service as the query coordinator430, the execution platform resource sends the request itself. In some examples, when it cannot be assured that the web socket is in the same global service as the query coordinator430, the query coordinator430performs the operation of sending back the response as there is already functionality to find the right global service instance for the query coordinator430.

FIG.5is an activity diagram of a method500of a data platform102in accordance with some examples. The data platform102uses the method500to implement a web application as a first-class database object.

In operation502, the data platform detects a data request from a browser402for a database object located on the data platform102and stored in database storage106.

In operation504, the data platform102instantiates a UDF server406within a security context of the data platform102based on a security policy determined by an owner of the database object.

In operation506, the data platform102instantiates a web application engine408of the UDF server406based on the security policy determined by the owner of the database object.

In operation508, the data platform102instantiates a user application410of the web application engine408based on the security policy determined by the owner of the database object.

In operation510, the data platform102communicates with the browser402using the web application engine408as a proxy server.

FIG.9illustrates a diagrammatic representation of a machine900in the form of a computer system within which a set of instructions may be executed for causing the machine900to perform any one or more of the methodologies discussed herein, according to examples. Specifically,FIG.9shows a diagrammatic representation of the machine900in the example form of a computer system, within which instructions902(e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine900to perform any one or more of the methodologies discussed herein may be executed. For example, the instructions902may cause the machine900to execute any one or more operations of any one or more of the methods described herein. In this way, the instructions902transform a general, non-programmed machine into a particular machine900(e.g., the compute service manager104, the execution platform110, and the data storage devices1to N of database storage106) that is specially configured to carry out any one of the described and illustrated functions in the manner described herein.

In alternative examples, the machine900operates as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine900may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine900may comprise, but not be limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a smart phone, a mobile device, a network router, a network switch, a network bridge, or any machine capable of executing the instructions902, sequentially or otherwise, that specify actions to be taken by the machine900. Further, while only a single machine900is illustrated, the term “machine” shall also be taken to include a collection of machines that individually or jointly execute the instructions902to perform any one or more of the methodologies discussed herein.

As mentioned above, a UI framework can be provided for users to build UIs for web applications within the database system and distribute the UI components to the consumers. The UI framework may be distributed along with application logic for the web application. This UI framework can embed the UI within the database system, making the consumer experience more seamless and secure as compared to accessing UIs outside of the database system (e.g., data platform102).

FIG.6illustrates a flow diagram for a method500for building and sharing UI components for a web application, according to some example embodiments. The UI component and web application may be created by a provider account and shared with one or more consumer accounts, for example, through a marketplace.

At operation602, a provider account creates a data application (e.g., web application) as a share object, which is identified as an application share. For example, the data application using the techniques described above (e.g., method500). For example, an installer stored procedure can be passed as a parameter to a creation flow, indicating that the share object is a data application. The client may grant usage on the installer to the share object. In some embodiments, the grants can be made automatically. A UI component is provided as part of the data application. Additional properties can be specified as to further customization of the data application. For example, the following command code fragment can be used to create the share object:CREATE SHARE<Webapp_name>INSTALLER=DB1.S1.INSTALLER

At operation604, the provider account may configure the data application using grant commands. These commands may create DB roles for the shared object. A grant command may be used for the UI component. For example, the following command code fragment can be used to grant usage of the UI component:GRANT USAGE ON WEBAPP<UI Component>TO SHARE<Webapp_name>

Other grant commands can be used to grant usage of database, schemas, tables, etc., linked to the web application. E.g.:GRANT USAGE ON DATABASE DB1 TO SHARE<Webapp_name>GRANT USAGE ON SCHEMA DB1.S1 TO SHARE<Webapp_name>GRANT SELECT ON TABLE DB1.S1.T1 TO SHARE<Webapp_name>

At operation606, the provider account may make the data application available for consumer accounts to use. For example, a provider account may bind the data application to a listing, such as a marketplace. For example, the following command code fragment can be used to bind the application to a listing:ALTER SHARE<Webapp_name>SET LISTING=‘LISTING’

At operation608, a consumer account may deploy the data application, which will then perform minimal installation operations. For example, the consumer account may discover the data application on the listing marketplace and select it for deployment. When the consumer account installs the shared object, a database (e.g., consumer database) may be created representing the share object (e.g., data application), and the consumer account can access the database as if it was a locally created database. The UI component may be part of the shared object as described above. For example, the following code fragment can be used to install the shared data application:CREATE DATABASE< >FROM SHARE PROVIDER.<Webapp_name>

At operation610, the consumer account may grant privileges to the data application instance. The consumer can grant privileges to the application that will be needed, either by the construction stored procedure or the runtime of the application. For example, the following command code fragment can be used to grant privileges:GRANT USAGE ON API INTEGRATION TO DATABASE< >

The UI component being part of the shared object is a defined object residing in the provider account rather than each of the consumer accounts that have deployed the web application. This feature allows the UI component to be on the server side and maintaining security barriers for the database system and the different accounts in the database system.

FIG.7illustrates an example UI700for a downloading tracking application. The UI700includes widgets, drop down menus, and other interactive components. These components can share states between the front-end browser and the backend, as described above. Moreover, the consumer account can further configure the UI components and add functionalities and features to the UI for its instance. Moreover, the UI components can be configured to access consumer account data.

UI700shows a number of downloads of an application “ABC” over a period. UI700shows a drop-down menu for selecting the start date and increment (e.g., weekly or monthly) for the download information. As discussed above, the consumer account can configure UI700to access consumer account data. For example, the UI700can compare package downloads of ABC with other packages (e.g., “XYZ”), for which information may be stored in the consumer account or other accounts.

FIG.8illustrates a computing environment for a UI component with a web application, according to some example embodiments. The computing environment includes a frontend and backend. The frontend includes a browser402executing on a client device112, as described above. A web application browser frontend (runtime) component802(also referred to as a UI component) is included in the browser402hosted by the remote data-processing device, as described above. The backend for the data platform100(e.g., compute service manager, execution platform) may include a UDF server406with a web application engine408running the web application408, as described above. A virtual machine (VM)806with a corresponding web application engine808running the web application810may also be provided. VM806can offer different infrastructure for different applications. For example, VM806can handle stateful operations because VMs can save the full memory state of an application. VM806can provide a strong security boundary, making additional system functions available.

Interaction between the frontend and backend may be governed by UI policies804. The UI policies804may restrict UI elements that can be used by applications (e.g., consumer account). The UI policies804can be configured to prevent data exfiltration and CRSF (Cross-Site Request Forgery) attacks from untrusted sources. The UI policies804can allow administrators to allow/disallow custom HTML, iFrames, and other third-party components. Moreover, the UI policies804may allow designation of trusted sources and allow management of third-party UI components from trusted sources.

Interaction between the UDF server406and virtual machine806may be governed by state policies812. The state policies812may match the execution environment of the web application410/810. The state policies812may allow the provider account (e.g., author) to determine whether the application410/810should be stateless or stateful and what type of resources are needed by the application410/810. Being stateful provides advantages in terms of speed and allowing additional types of interactions (e.g., interactions relying on libraries, which in turn rely on data in memory). The system may maintain running the stateful applications without stopping it to maintain the stateful nature. Being stateless can be more reliable in some instances because there is no single “process” that needs to run a request. All the processes retrieve their information from other queries or interactions.

The machine900includes processors904, memory906, and I/O components908configured to communicate with each other such as via a bus910. In an example, the processors904(e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, multiple processors as exemplified by processor912and a processor914that may execute the instructions902. The term “processor” is intended to include multi-core processors that may comprise two or more independent processors (sometimes referred to as “cores”) that may execute instructions902contemporaneously. AlthoughFIG.9shows multiple processors904, the machine900may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiple cores, or any combination thereof.

The memory906may include a main memory932, a static memory916, and a storage unit918including a machine storage medium934, all accessible to the processors904such as via the bus910. The main memory932, the static memory916, and the storage unit918store the instructions902embodying any one or more of the methodologies or functions described herein. The instructions902may also reside, completely or partially, within the main memory932, within the static memory916, within the storage unit918, within at least one of the processors904(e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine900.

The input/output (I/O) components908include components to receive input, provide output, produce output, transmit information, exchange information, capture measurements, and so on. The specific I/O components908that are included in a particular machine900will depend on the type of machine. For example, portable machines such as mobile phones will likely include a touch input device or other such input mechanisms, while a headless server machine will likely not include such a touch input device. It will be appreciated that the I/O components908may include many other components that are not shown inFIG.9. The I/O components908are grouped according to functionality merely for simplifying the following discussion and the grouping is in no way limiting. In various examples, the I/O components908may include output components920and input components922. The output components920may include visual components (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), acoustic components (e.g., speakers), other signal generators, and so forth. The input components922may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point-based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or another pointing instrument), tactile input components (e.g., a physical button, a touch screen that provides location and/or force of touches or touch gestures, or other tactile input components), audio input components (e.g., a microphone), and the like.

Communication may be implemented using a wide variety of technologies. The I/O components908may include communication components924operable to couple the machine900to a network936or devices926via a coupling930and a coupling928, respectively. For example, the communication components924may include a network interface component or another suitable device to interface with the network936. In further examples, the communication components924may include wired communication components, wireless communication components, cellular communication components, and other communication components to provide communication via other modalities. The devices926may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a universal serial bus (USB)). For example, as noted above, the machine900may correspond to any one of the compute service manager104, the execution platform110, and the devices926may include the data storage device226or any other computing device described herein as being in communication with the data platform102or the database storage106.

The various memories (e.g.,906,916,932, and/or memory of the processor(s)904and/or the storage unit918) may store one or more sets of instructions902and data structures (e.g., software) embodying or utilized by any one or more of the methodologies or functions described herein. These instructions902, when executed by the processor(s)904, cause various operations to implement the disclosed examples.

As used herein, the terms “machine-storage medium,” “device-storage medium,” and “computer-storage medium” mean the same thing and may be used interchangeably in this disclosure. The terms refer to a single or multiple storage devices and/or media (e.g., a centralized or distributed database, and/or associated caches and servers) that store executable instructions and/or data. The terms shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media, including memory internal or external to processors. Specific examples of machine-storage media, computer-storage media, and/or device-storage media include non-volatile memory, including by way of example semiconductor memory devices, e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), field-programmable gate arrays (FPGAs), and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms “machine-storage media,” “computer-storage media,” and “device-storage media” specifically exclude carrier waves, modulated data signals, and other such media, at least some of which are covered under the term “signal medium” discussed below.

In various examples, one or more portions of the network936may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local-area network (LAN), a wireless LAN (WLAN), a wide-area network (WAN), a wireless WAN (WWAN), a metropolitan-area network (MAN), the Internet, a portion of the Internet, a portion of the public switched telephone network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi® network, another type of network, or a combination of two or more such networks. For example, the network936or a portion of the network936may include a wireless or cellular network, and the coupling930may be a Code Division Multiple Access (CDMA) connection, a Global System for Mobile communications (GSM) connection, or another type of cellular or wireless coupling. In this example, the coupling930may implement any of a variety of types of data transfer technology, such as Single Carrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized (EVDO) technology, General Packet Radio Service (GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE) technology, third Generation Partnership Project (3GPP) including 3G, fourth generation wireless (4G) networks, fifth generation wireless (5G) networks, Universal Mobile Telecommunications System (UMTS), High-Speed Packet Access (HSPA), Worldwide Interoperability for Microwave Access (WiMAX), Long Term Evolution (LTE) standard, others defined by various standard-setting organizations, other long-range protocols, or other data transfer technology.

The instructions902may be transmitted or received over the network936using a transmission medium via a network interface device (e.g., a network interface component included in the communication components924) and utilizing any one of a number of well-known transfer protocols (e.g., hypertext transfer protocol (HTTP)). Similarly, the instructions902may be transmitted or received using a transmission medium via the coupling928(e.g., a peer-to-peer coupling) to the devices926. The terms “transmission medium” and “signal medium” mean the same thing and may be used interchangeably in this disclosure. The terms “transmission medium” and “signal medium” shall be taken to include any intangible medium that is capable of storing, encoding, or carrying the instructions902for execution by the machine900, and include digital or analog communications signals or other intangible media to facilitate communication of such software. Hence, the terms “transmission medium” and “signal medium” shall be taken to include any form of modulated data signal, carrier wave, and so forth. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.

The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Similarly, the methods described herein may be at least partially processor-implemented. For example, at least some of the operations of the methodologies disclosed herein may be performed by one or more processors. The performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but also deployed across a number of machines. In some examples, the processor or processors may be located in a single location (e.g., within a home environment, an office environment, or a server farm), while in other examples the processors may be distributed across a number of locations.

Although the examples of the present disclosure have been described with reference to specific examples, it will be evident that various modifications and changes may be made to these examples without departing from the broader scope of the inventive subject matter. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific examples in which the subject matter may be practiced. The examples illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other examples may be used and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various examples is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

Such examples of the inventive subject matter may be referred to herein, individually and/or collectively, by the term “example” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed. Thus, although specific examples have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific examples shown. This disclosure is intended to cover any and all adaptations or variations of various examples. Combinations of the above examples, and other examples not specifically described herein, will be apparent, to those of skill in the art, upon reviewing the above description.

In this document, the terms “a” or “an” are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of “at least one” or “one or more.” In this document, the term “or” is used to refer to a nonexclusive or, such that “A or B” includes “A but not B,” “B but not A,” and “A and B,” unless otherwise indicated. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein.” Also, in the following claims, the terms “including” and “comprising” are open-ended; that is, a system, device, article, or process that includes elements in addition to those listed after such a term in a claim is still deemed to fall within the scope of that claim.

Described implementations of the subject matter can include one or more features, alone or in combination as illustrated below by way of example.

Example 1. A method comprising: generating, by a provider account in a data system, a data application including a user interface (UI) component, the data application being a share object in a database; configuring the data application for sharing with other accounts using one or more grant commands; sharing the data application with a consumer account in the data system; deploying, by the consumer account, the data application, the consumer account being given a set of privileges based on the one or more grant commands; and operating, by the consumer account, the UI component based on the share object residing in the provider account.

Example 2. The method of example 1, further comprising: creating, by the consumer account, a consumer database representing the share object.

Example 3. The method of any of examples 1-2, wherein the share object remains behind a security barrier associated with the provider account while the data application is deployed by the consumer account.

Example 4. The method of any of examples 1-3, further comprising: customizing, by the consumer account, the UI component, wherein the UI component is configured to access consumer account data.

Example 5. The method of any of examples 1-4, further comprising: instantiating a User Defined Function (UDF) server within a security context of the data system based on a security policy determined by the provider account; instantiating an application engine of the UDF server based on the security policy determined by provider account; instantiating the data application of the application engine based on the security policy determined by provider account; and communicating by the data application with a browser using the application engine as a proxy server.

Example 6. The method of any of examples 1-5, wherein communication between the browser and the UDF server is governed by a set of UI policies, the set of UI policies restricting a set of elements that can be used by the consumer account.

Example 7. The method of any of examples 1-6, wherein communication between the UDF server and a virtual machine provided in the data system running the data application is governed by a set of state policies, the state policies matching an environment of the UDF server and the virtual machine.

Example 8. A system comprising: one or more processors of a machine; and a memory storing instructions that, when executed by the one or more processors, cause the machine to perform operations implementing any one of example methods 1 to 7.

Example 9. A machine-readable storage device embodying instructions that, when executed by a machine, cause the machine to perform operations implementing any one of example methods 1 to 7.