Abstract: Trace data generated by a set of executing business asset components of a plurality of business asset components that form a business process application are received. Source code that defines the plurality of business asset components is received. Based on the trace data and the source code, native binary executable code is generated for a first subset of the business asset components and interpretable code for a second subset of business asset components is maintained.

Abstract: Techniques for processing change requests for software projects are disclosed. An example method includes generating a contributor score for a contributor of source code to a software project and saving the contributor score to a storage device. The contributor score reflects a degree to which source code submissions by the contributor are trustworthy. The method also includes receiving a change request from the contributor to change a part of the software project. The change request includes new or updated source code for the software project. The method also includes, in response to receiving the change request, retrieving the contributor score from the storage device, comparing, by a processing device, the contributor score to a threshold to identify an action to be performed in relation to the change request, and executing the action.

Abstract: A system includes a memory and a processor, where the processor is in communication with the memory. The processor is configured to receive a request to compress a schema. The schema is analyzed to determine whether to apply a first type of compression or a second type of compression, where analyzing the schema includes determining whether the schema exceeds a threshold level. Upon determining that the schema exceed the threshold level, a compressed schema is generated by performing the second type of compression. Next, the processor responds to the request with the compressed schema.

Abstract: Systems and methods for generating asynchronous application programming interface (API) documents are generally described. In various examples, a topic discovery request may be sent to a message broker. A list of topics may be received from the message broker. First identifier data identifying a first topic of the list of topics may be received from the message broker. A first message may be received from the message broker, where the first message pertains to the first topic. First schema may be determined using the first message. The first schema data may describe content of the first message and organization of the content of the first message. The first identifier data may be stored in a first data structure in association with the first schema data.

Abstract: Systems and methods for implementing a build-time, automatic, exporter configuration rule generator that removes the need for manual definition of exporter configurations are described. A processing device may perform a scan of source code of an application to identify one or more classes of the application, each of the one or more classes enabling an exporter to access metrics generated by the class. For each of the one or more classes, the processing device may analyze source code of the class with a set of templates and heuristics to generate a set of configuration rules for the class. The processing device may then generate an exporter configuration for the exporter based on the set of configuration rules for each of the one or more classes.

Abstract: Systems and methods for generating SLO specifications using annotations are generally described. In various examples, first source code associated with a first computer-implemented service is received. In various cases, a first annotation in the first source code may be received. The first annotation may include first metadata defining a name of an SLO specification. A second annotation in the first source code may be received. The second annotation may include second metadata defining a service-level objective (SLO) of a first aspect of the first computer-implemented service. In some cases, the first computer-implemented service may be executed using the first source code. In various examples, the SLO specification may be generated based on the first annotation and the second annotation.

Abstract: In various examples disclosed herein, provided is a method for generating metadata to facilitate code generation. The method can include receiving a first file that includes information relating to a first set of components in a first notation syntax and a second file that includes information relating to a second set of components in a second notation syntax. The method can also include cross-validating the first file and the second file to determine that a first reference, in a first component of the first set of components, to a second component of the second set of components is valid. The method can also include generating a first metadata file that includes identification information relating to the first reference. The method can also include generating code to be executed based on the first metadata file, the first file, and the second file.

Abstract: A method includes adding, by a processing device, an operator to a group of operators to be installed on a containerized computing services platform, determining, by the processing device, whether the group of operators is complete, and responsive to determining that the group of operators is complete, generating, by the processing device based on a set of meta-operator parameters comprising a meta-operator identifier, a meta-operator comprising instructions for managing installation of the group of operators on the containerized computing services platform.

Abstract: In one example, a system can identify application programming interface (API) object classes specified in a definition file. The definition file can be for a target API object. The system can then update an attribute field associated with the target API object to specify the API object classes. Operator software in a distributed computing environment can be configured to monitor the API object classes specified in the attribute field of the target API object and execute computing logic in response to events related to the API object classes.

Abstract: Removing inactive components to facilitate code generation. A first file that includes a first group of components in a first notation syntax and a second file that includes a second group of components in a second notation syntax is received. A first set of inactive components of the first group of components is identified. A second set of inactive components of the second group of components is identified. The components of the first group of components and the second group of components that are not marked as inactive components are active components. Code to be executed based on the active components is generated.

Abstract: In various examples disclosed herein, provided is a method for segmenting processes into stand-alone services. The method can include receiving a file that includes information relating to a plurality of components. The method can also include determining a first resource cost associated with deploying each component in a respective service and a second resource cost associated with deploying each component in a single service. The method can also include determining a segmentation plan that segments the plurality of components into groups of one or more components that can be executed by respective services, where a third resource cost associated with the segmentation plan is lower than the first resource cost and the second resource cost. The method can also include generating instructions to deploy the respective services on the one or more computing devices.

Abstract: In various examples disclosed herein, provided is a method for mapping data models to facilitate code generation. The method can include receiving a first file comprising a first data model of a first group of components and a second file comprising a second data model of a second group of components. The method can also include converting the first data model into a first intermediate data model. The method can also include converting the second data model into a second intermediate data model. The method can also include mapping the first intermediate data model to the second intermediate data model to generate a map of matching elements. The method can also include generating code to be executed based at least in part on the map of matching elements.

Abstract: Systems and methods for providing message schema migration in messaging systems. In one implementation, a definition of a messaging schema is received. One or more transformation files associated with the messaging schema is received, wherein the one or more transformation files define a plurality of transformations to be applied to incoming messages. An order of applying the plurality of transformations is determined. The plurality of transformations is applied to a message of the incoming messages according to the determined order. The message is forwarded to a messaging system.

Abstract: In one example described herein, a processing device can receive computing metrics from nodes within a mesh network. The processing device can use those computing metrics to derive a maximum message size based on the capabilities of the nodes within the mesh network. The processing device can then transmit the maximum message size to nodes within the mesh network so that the nodes can generate messages that do not exceed the maximum message size.

Abstract: In various examples disclosed herein, provided is a method and system for cross-validating files to facilitate code generation. The system can perform the cross-validation in phases of disparate files to enable the interoperability of the files. The files can include representations of tasks that are organized differently and differ in format and semantics. The method and system described herein can perform syntax and semantic validation on the files to check for errors, and then identify terms and names identified in the tasks associated with the files along with signatures (e.g., schemas for data models or function signatures for function invocations) associated with the names. After error checking is complete, and after the names and signatures are identified, the names and signatures in the respective files can be cross-validated to find matching tasks, and code is generated that utilizes the cross-validated and matching tasks.

Abstract: Systems and methods for providing a presentation mode for application programming interface functions. In one implementation, a first selection pertaining to one or more API functions of a plurality of API functions is received, via a user interface, wherein the first selection indicates an order of execution of the one or more API functions for a task. A second selection is received indicating a relationship between at least two of the API functions of the plurality of API functions. The relationship between the at least two API functions is set according to the second selection. The one or more API functions are caused, by the processing device, to be arranged according to the first selection. The one or more API functions are presented, via the user interface, arranged according to the first selection.

Abstract: Systems and methods for cloud-based keyless entry are generally described. In some examples, a first number is received from a vehicle. A first computing device of the vehicle may be configured to control an electronic door lock. A first unlock code may be generated using the first number. In some examples, a notification is sent to a remote entry device associated with the vehicle. A response to the notification may be received from the remote entry device. In some examples, the first number may be retrieved from a messaging service based at least in part on the receiving the response to the notification. A second unlock code may be generated using the first number. A determination may be made that the first unlock code matches the second unlock code. An instruction may be sent to the first computing device, the instruction effective to cause unlock of the electronic door lock.

Abstract: It is determined that an interpretable application including a plurality of files utilizes a runtime loaded external dependency that includes a plurality of functions. The runtime loaded external dependency includes executable software instructions that are loaded into the interpretable application during a runtime of the interpretable application in a web browser. A runtime dependency header module that contains information that identifies, for each function of the plurality of functions, a name of the function and a number of parameters of the function is obtained. The runtime dependency header module is stored in a location used by an interactive development environment (IDE) to determine dependencies used by the interpretable application for purposes of an autocompletion feature of the IDE.

Abstract: Systems and methods for generating SLO specifications using annotations are generally described. In various examples, first source code associated with a first computer-implemented service is received. In various cases, a first annotation in the first source code may be received. The first annotation may include first metadata defining a name of an SLO specification. A second annotation in the first source code may be received. The second annotation may include second metadata defining a service-level objective (SLO) of a first aspect of the first computer-implemented service. In some cases, the first computer-implemented service may be executed using the first source code. In various examples, the SLO specification may be generated based on the first annotation and the second annotation.

Abstract: Events associated with a virtual machine can be used to adjust an amount of resource objects that may be allocated from a resource pool for the virtual machine. For example, a system can receive a notification including event data indicating an event related to the virtual machine, wherein the virtual machine is configured to rely on resource objects in a resource pool for performing one or more computing operations. The system can determine that the event is a particular type of event. Based on determining that the event is the particular type of event, the system can select a scaling policy corresponding to the particular type of event. The system can then apply the scaling policy to the event data to determine a scaling strategy for adjusting the amount of resource objects.