An efficient structure and methodology are provided for communicating in a network using a contract implemented in a packet or frame. In various embodiments, a user can generate a contract clause having a constraint for communicating in the network, and determine a communication layer at which to process the constraint during communication in the network. The user device can insert the contract clause in a position in a packet corresponding to the communication layer and can transmit the packet from the user device. In various embodiments, a network node that receives a packet can identify a contract clause in a packet and can process a constraint from the contract clause. The network node can track performance of the constraint and provide accountability in response to the tracking of the performance with respect to terms associated with the constraint in the contract clause.

A method includes identifying a quality of service (QoS) policy associated with a tenant in view of a tenant identifier. The QoS policy includes a threshold value of a performance parameter. The method also includes receiving a service request from the tenant, estimating, in view of a subset of a plurality of historical records, an impact value indicating an impact of the service request on the performance parameter of the distributed storage system, determining, in view of the impact value, an estimated value of the performance parameter to result from servicing the service request of the tenant, and responsive to an evaluation of the estimated value of the performance parameter in view of the threshold value of the performance parameter, allocating computing resources of the multi-tenant distributed storage system to execute an operation associated with the service request.

Systems and methods for configuration vulnerability checking and remediation are provided. The systems provided herein identify risk based upon service indications of a particular configuration, such that automated risk analysis may be facilitated.

Systems and methods for configuration vulnerability checking and remediation are provided. The systems provided herein identify risk based upon service indications of a particular configuration, such that automated risk analysis may be facilitated.

Technologies are described for determining between synchronous and asynchronous modes for computing service requests. Computing service requests are received by a computing service from clients. The computing service dynamically determines whether to use synchronous mode or asynchronous mode for processing the computing service requests. The computing service makes the dynamic determination of which mode to use (synchronous or asynchronous) based on various criteria, which can include synchronous/asynchronous mode recommendations generated by machine learning models and/or synchronous/asynchronous mode recommendations generated by static rules.

Technologies are described for determining between synchronous and asynchronous modes for computing service requests. Computing service requests are received by a computing service from clients. The computing service dynamically determines whether to use synchronous mode or asynchronous mode for processing the computing service requests. The computing service makes the dynamic determination of which mode to use (synchronous or asynchronous) based on various criteria, which can include synchronous/asynchronous mode recommendations generated by machine learning models and/or synchronous/asynchronous mode recommendations generated by static rules.

Techniques described herein relate to a method for deploying workflows. The method may include receiving, at a service controller of a federated controller, a request to deploy a workflow in a device ecosystem; decomposing, by the service controller, the workflow into a plurality of workflow portions; performing, by the service controller, a search in a capabilities and constraints data construct to identify a domain in which to perform a workflow portion of the plurality of workflow portions; providing the workflow portion and workflow constraints to a platform controller in the domain; performing, by the platform controller, a subgraph similarity check to determine that a previously executed workflow portion was successfully executed on a subgraph in the domain; provisioning, by the platform controller, a set of devices in the domain based on the subgraph; and executing the workflow portion in the domain.

Generally discussed herein are systems, devices, and methods for data management in a reverse content data network (rCDN). A component of the rCDN may include a memory to hold content received from a first sensor device of a plurality of sensor devices of the rCDN and first attributes that describe properties of the content. The component may include processing circuitry to receive second content from a second sensor device of the plurality of sensor devices, the second content including a plurality of second attributes that describe properties of the second content, and forward, in response to a determination, based on the first and second attributes, that there is insufficient space to store the second content on the memory, the second content to a node of the rCDN that is fewer hops away from a backend cloud than the component.

Generally discussed herein are systems, devices, and methods for data management in a reverse content data network (rCDN). A component of the rCDN may include a memory to hold content received from a first sensor device of a plurality of sensor devices of the rCDN and first attributes that describe properties of the content. The component may include processing circuitry to receive second content from a second sensor device of the plurality of sensor devices, the second content including a plurality of second attributes that describe properties of the second content, and forward, in response to a determination, based on the first and second attributes, that there is insufficient space to store the second content on the memory, the second content to a node of the rCDN that is fewer hops away from a backend cloud than the component.

An example computing device is configured to receive an instance of a customer service model representative of a plurality of customer services. Each of the plurality of customer services associated with a corresponding at least one requirement and a corresponding at least one constraint. The computing device is configured to receive an instance of a resource model representative of a plurality of resources and map the instance of the customer service model and the instance of the resource model to an internal placement model. The computing device is configured to allocate the plurality of resources to the plurality of customer services such that the at least one requirement and the at least one constraint for each of the plurality of customer services are satisfied and inverse map data indicating how the plurality of resources are allocated to a format consumable by the customer device and output the inverse mapped data.