Abstract: A method may include generating, by a source isolate, an external object reference, passing, by the source isolate, the external object reference to a target isolate, storing, by the source isolate and in an exported reference table, an entry that maps the external object reference to an object stored in a heap of the source isolate, performing, by the target isolate, a task that accesses the object using the external object reference, receiving, by the source isolate and from a finalizer of the external object reference, a notification that the external object reference has become unreferenced, and in response to the notification, removing, by the source isolate, the entry from the exported reference table.

Abstract: A method may include generating, by a source isolate, an external object reference, passing, by the source isolate, the external object reference to a target isolate, storing, by the source isolate and in an exported reference table, an entry that maps the external object reference to an object stored in a heap of the source isolate, performing, by the target isolate, a task that accesses the object using the external object reference, receiving, by the source isolate and from a finalizer of the external object reference, a notification that the external object reference has become unreferenced, and in response to the notification, removing, by the source isolate, the entry from the exported reference table.

Abstract: Systems and methods to identify to iteratively accomplish a complex task by mapping the complex task into a series of smaller tasks and then to reduce the task by executing one or more of the smaller tasks. Such a system ensures that a user does not have to be familiar with the operational environment of the platform (governance rules, architecture, and the like) when scripting tasks. Instead, the user can concentrate on the logic or purpose of the task, and various embodiments of the system will “intelligently” process/execute the task in the most efficient way, without violating the governance constraints imposed on users or accounts as part of the multi-tenant environment. Among other benefits, this approach permits users to more efficiently describe desired tasks and hence to more effectively utilize the platform.

Abstract: Systems, apparatuses, and methods for scheduling the processing of job requests on a data processing platform that utilizes multiple processing elements. In one embodiment, each job request includes a set of attributes that are used to determine scheduling and handling. Such attributes may include job type, priority, priority time, dependency list, and fail on dependency failure flag. In one embodiment, job requests are started in an order determined by the job request attributes of priority and priority time. If a job request has an unresolved dependency, the job request may be removed from the ordered list. Thus, a lower-priority job request may overtake a higher priority job if the higher-priority job has unfinished dependent job requests. Rules for interacting with job requests having these attributes may be customized according to user needs and desires.

Abstract: Systems and methods to identify to iteratively accomplish a complex task by mapping the complex task into a series of smaller tasks and then to reduce the task by executing one or more of the smaller tasks. Such a system ensures that a user does not have to be familiar with the operational environment of the platform (governance rules, architecture, and the like) when scripting tasks. Instead, the user can concentrate on the logic or purpose of the task, and various embodiments of the system will “intelligently” process/execute the task in the most efficient way, without violating the governance constraints imposed on users or accounts as part of the multi-tenant environment. Among other benefits, this approach permits users to more efficiently describe desired tasks and hence to more effectively utilize the platform.