Abstract: Data is received characterizing a virtual resource requirement for deployment of a resource in a first remote computing environment and/or a second remote computing environment. Second data is received characterizing resource cost for the first remote computing environment and the second remote computing environment. The receiving the second data includes accessing, via an application programming interface of the first remote computing environment and based on an account identity of an entity associated with the virtual resource requirement, the second data characterizing computing resource cost for the first remote computing environment. A first cost for deploying the resource within the first remote computing environment and a second cost for deploying the resource within the second remote computing environment is predicted using the received data. The first cost and the second cost is provided. Related apparatus, systems, techniques and articles are also described.

Abstract: Data characterizing a log of requests by a plurality of software services executing based on a virtual resource that is within a remote computing environment is received. The executing includes transmitting the requests for utilization of the virtual resource. A metric of utilization of the virtual resource by a first software service of the plurality of software services is determined based on the log. The metric of utilization characterizes a portion of total usage of the virtual resource that is attributable to the first software service. The metric of utilization is provided. Related apparatus, systems, techniques and articles are also described.

Abstract: Data characterizing a first address of a software service executing based on a first virtual resource that is within a remote computing environment is received. The executing includes transmitting a request for utilization of the first virtual resource. The received data further characterizes a log of the request for the first virtual resource. The log includes the first address and a second address of the first virtual resource. A mapping between the first address of the software service and the second address of the first virtual resource is determined using the received data. The mapping between the first address of the software service and the second address of the first virtual resource is provided. Related apparatus, systems, techniques and articles are also described.

Abstract: A method for updating cloud resource tags is provided. The tag associated with a cloud resource may assign the cloud resource to one or more categories to enable tracking of the cloud resource. The method may include determining, based on a synchronization profile, the scope of the update. For example, the scope of the update may encompass individual resources, groups of resources, and/or subscriptions. A metadata data store may be queried to retrieve mapping rules corresponding to tags of resources from one or more cloud service providers that are within the scope of the update. If the value of a tag does not match the value specified by the corresponding mapping rule, the value of the tag may be updated to match the value specified by the mapping rule. Related systems and articles of manufacture, including computer program products, are also provided.

Abstract: Data is received characterizing a plurality of virtual resources executing application code and deployed within a remote computing environment. The remote computing environment is providing a first configuration of computing resources for execution of the plurality of virtual resources. Resource consumption information associated with the plurality of virtual resources is monitored via an application programing interface of the remote computing environment. A second configuration of computing resources for the plurality of virtual resources is determined using a set of rules and the resource consumption information. A request is transmitted to the remote computing environment to provide the second configuration of computing resources for execution of the plurality of virtual resources. Related apparatus, systems, techniques and articles are also described.

Abstract: Data is received characterizing a virtual resource requirement for deployment of a resource in a first remote computing environment and/or a second remote computing environment. Second data is received characterizing resource cost for the first remote computing environment and the second remote computing environment. The receiving the second data includes accessing, via an application programming interface of the first remote computing environment and based on an account identity of an entity associated with the virtual resource requirement, the second data characterizing computing resource cost for the first remote computing environment. A first cost for deploying the resource within the first remote computing environment and a second cost for deploying the resource within the second remote computing environment is predicted using the received data. The first cost and the second cost is provided. Related apparatus, systems, techniques and articles are also described.

Abstract: Methods and systems are described for cross-cloud call detection. The system may include detecting an instruction configured to call a resource. The instruction may include a name indicative of the resource and one or more values. The resource is configured to construct code using the one or more values. The system may determine the resource is incompatible with a service based on at least the name and the one or more values of the instruction. A conversion of source code is halted when the resource is incompatible with the service.

Abstract: Methods, systems, and non-transitory computer-readable media are described herein. In some embodiments, a computing platform may deploy a cloud application comprising a first instance of the cloud application. Further, the computing platform may direct a DNS to the first instance of the cloud application. Next, the computing platform may determine that a second instance of the cloud application should be deployed. Additionally, the computing platform may create a first global traffic manager configured with at least a first endpoint and a second endpoint, where the first endpoint is associated with the first instance and is enabled, and where the second endpoint is associated with the second instance, and is disabled. Subsequently, the computing platform may direct the DNS to the first global traffic manager. The computing platform may then direct the DNS to the first global traffic manager, enable the second endpoint.

Abstract: Described embodiments provide systems and methods for stateless modification of operating system registry data across network boundaries. The system includes a processor coupled to memory and configured to execute instructions to receive, within a first network, a request to apply a modification to an operating system registry of a second device within a second network different from the first network. The processor queues data describing the requested modification, receives a polling request from the second device, and transmits, to the second device responsive to the polling request, the queued data describing the requested modification for the second device to apply to the operating system registry of the second device. For example, the requested modification may be to create a key, to create a value, to delete a key, or to delete a value.

Abstract: Described embodiments provide systems and methods for stateless modification of operating system registry data across network boundaries. The system includes a processor coupled to memory and configured to execute instructions to receive, within a first network, a request to apply a modification to an operating system registry of a second device within a second network different from the first network. The processor queues data describing the requested modification, receives a polling request from the second device, and transmits, to the second device responsive to the polling request, the queued data describing the requested modification for the second device to apply to the operating system registry of the second device. For example, the requested modification may be to create a key, to create a value, to delete a key, or to delete a value.

Abstract: Techniques for implementing a non-relational database that makes efficient use of collections within the database. For one or more collections, two or more sub-collections can be created for storing documents. Each collection can be configured as a single partition entity or a partitioned entity within the database. Each sub-collection is identified by a sub-collection identifier. If the collection is configured as a partitioned entity, then a partition key can be determined for documents to be accessed in the collection. The partition key can be extended with the sub-collection ID to form a compound property (sub-collection ID, partition key) that determines placements of the respective documents in the identified sub-collection across partitions of the collection. If the collection is configured as a single partition entity, then a field for the partition key is ignored and the respective documents are placed in the identified sub-collection within the single partition of the collection.

Abstract: Methods and systems for routing a user request for a service to a version of the service in a geographical region associated with the user are described herein. The service may be deployed in multiple geographical regions, and the service may have multiple versions in each of the geographical regions. A user device may send a request for a service to a first server in a geographical region. The first server may determine whether the user is associated with the geographical region. Responsive to determining that the user is not associated with the geographical region, the first server may ask one or more servers in other geographical regions whether the user is associated with any of the other geographical regions.

Abstract: Techniques for implementing a non-relational database that makes efficient use of collections within the database. For one or more collections, two or more sub-collections can be created for storing documents. Each collection can be configured as a single partition entity or a partitioned entity within the database. Each sub-collection is identified by a sub-collection identifier. If the collection is configured as a partitioned entity, then a partition key can be determined for documents to be accessed in the collection. The partition key can be extended with the sub-collection ID to form a compound property (sub-collection ID, partition key) that determines placements of the respective documents in the identified sub-collection across partitions of the collection. If the collection is configured as a single partition entity, then a field for the partition key is ignored and the respective documents are placed in the identified sub-collection within the single partition of the collection.

Abstract: Methods and systems for routing a user request for a service to a version of the service in a geographical region associated with the user are described herein. The service may be deployed in multiple geographical regions, and the service may have multiple versions in each of the geographical regions. A user device may send a request for a service to a first server in a geographical region. The first server may determine whether the user is associated with the geographical region. Responsive to determining that the user is not associated with the geographical region, the first server may ask one or more servers in other geographical regions whether the user is associated with any of the other geographical regions.

Abstract: Described embodiments automatically and dynamically generate and update resource templates for deployable resources, utilizing composable parts that may be dynamically replaced. Common portions of the templates may be easily defined once and reused multiple times, reducing risk of error and ensuring stability and cross-resource compatibility. Each dynamic template may have replaceable parts, as well as replaceable parameters and values within the replaceable parts, as well as in common portions of the template. The replacement properties and values may be determined at runtime or during deployment, ensuring that configurations are always current.

Abstract: Methods, systems, and non-transitory computer-readable media are described herein. In some embodiments, a computing platform may deploy a cloud application comprising a first instance of the cloud application. Further, the computing platform may direct a DNS to the first instance of the cloud application. Next, the computing platform may determine that a second instance of the cloud application should be deployed. Additionally, the computing platform may create a first global traffic manager configured with at least a first endpoint and a second endpoint, where the first endpoint is associated with the first instance and is enabled, and where the second endpoint is associated with the second instance, and is disabled. Subsequently, the computing platform may direct the DNS to the first global traffic manager. The computing platform may then direct the DNS to the first global traffic manager, enable the second endpoint.

Abstract: The systems and methods described herein determine metrics of cardiac or vascular performance, such as cardiac output, and can use the metrics to determine appropriate levels of mechanical circulatory support to be provided to the patient. The systems and methods described determine cardiac performance by determining aortic pressure measurements (or other physiologic measurements) within a single heartbeat or across multiple heartbeats and using such measurements in conjunction with flow estimations or flow measurements made during the single heartbeat or multiple heartbeats to determine the cardiac performance, including determining the cardiac output. By utilizing a mechanical circulatory support system placed within the vasculature, the need to place a separate measurement device within a patient is reduced or eliminated. The system and methods described herein may characterize cardiac performance without altering the operation of the heart pump (e.g., without increasing or decreasing pump speed).

Abstract: A technique for managing a read cache in an eventually-consistent data store includes, in response to a read request for a specified data element, receiving the specified data element from the read cache as well as a remaining TTL (time to live) of the data element, as indicated by a timer for that data element in the read cache. If the remaining TTL falls below a predetermined value, the technique triggers an early refresh of the specified data element, prior to its expiration. Consequently, later-arriving read requests to the same data element that arrive before the data element has been refreshed experience cache hits, thus avoiding the need to perform their own time-consuming refresh operations.

Abstract: Methods, systems, and non-transitory computer-readable media are described herein. In some embodiments, a computing platform may deploy a cloud application comprising a first instance of the cloud application. Further, the computing platform may direct a DNS to the first instance of the cloud application. Next, the computing platform may determine that a second instance of the cloud application should be deployed. Additionally, the computing platform may create a first global traffic manager configured with at least a first endpoint and a second endpoint, where the first endpoint is associated with the first instance and is enabled, and where the second endpoint is associated with the second instance, and is disabled. Subsequently, the computing platform may direct the DNS to the first global traffic manager. The computing platform may then direct the DNS to the first global traffic manager, enable the second endpoint.

Abstract: The systems and methods described herein determine metrics of cardiac performance via a mechanical circulatory support device and use the cardiac performance to calibrate, control and deliver mechanical circulatory support for the heart. The systems include a controller configured to operate the device, receive inputs indicative of device operating conditions and hemodynamic parameters, and determine vascular performance, including vascular resistance and compliance, and native cardiac output. The systems and methods operate by using the mechanical circulatory support device (e.g., a heart pump) to introduce controlled perturbations of the vascular system and, in response, determine heart parameters such as stroke volume, vascular resistance and compliance, left ventricular end diastolic pressure, and ultimately determine native cardiac output.