Abstract: Some embodiments of the invention provide a novel method for programming the management, control and data planes of a software-defined network (SDN) in a unified way. Some embodiments use a transactional database to store the management plane state, and implement the control plane with a specialized query language that, when compiled, automatically executes in an incremental fashion, which improves the scalability of the control plane. For instance, in response to a change, the controller does not re-compute and redistribute the entire network state. Instead, it performs an incremental amount of work proportional to the size of modified state, not of the entire network state. Some embodiments use Differential Datalog (DDlog) for the control plane to compute over relations and collections, and to offer automatic incremental updates. To aid correctness, some embodiments type-check together the management, control and data planes, and use automated tools to generate most code for data movement between planes.

Abstract: A computer implemented processing service for efficient streaming of data input from one or more sources to one or more receivers is disclosed. The processing service includes a schema manager that receives commands from a tenant of the data stream processing service. The processing service includes a processing services gateway that validates the data and sends the data to a transformation processor. The transformation processor receives the data and parses the data into the one or more data formats in accordance with the instructions and sends the data in the one or more data formats to an egress service. The egress service outputs the data in the one or more data formats to the one or more receivers, each receiver receiving the data in a data pipeline in one of the one or more formats.

Abstract: A computer implemented processing service for efficient streaming of data input from one or more sources to one or more receivers is disclosed. The processing service includes a schema manager that receives commands from a tenant of the data stream processing service. The processing service includes a processing services gateway that validates the data and sends the data to a transformation processor. The transformation processor receives the data and parses the data into the one or more data formats in accordance with the instructions and sends the data in the one or more data formats to an egress service. The egress service outputs the data in the one or more data formats to the one or more receivers, each receiver receiving the data in a data pipeline in one of the one or more formats.

Abstract: A computer-implemented method of receiving and incrementally processing hierarchical data in a computing environment. Receiving hierarchical data within a computing environment. The computing environment including a plurality of interrelated components. Incrementally processing the hierarchical data to obtain processed portions. The incremental processing of the portions of hierarchical data able to be initiated with requiring receipt of the entirety of the hierarchical data. Maintaining an indexed representation of previously processed portions of the hierarchical data to prevent unnecessarily processing a same portion of the hierarchical data.

Abstract: Example methods and systems for routing domain computation are described. In one example, a computer system may assign multiple logical entities with respective routing domain identifiers (IDs) by processing network topology information using multiple compute nodes. In response to detecting a network topology change associated with a particular logical entity, the computer system may determine first state change information identifying a first update to first state information maintained by a first compute node; and second state change information identifying a second update to second state information maintained by a second compute node. Further, the particular logical entity with an updated routing domain ID based on the first state change information and the second state change information. The updated routing domain ID may be used in a communication between a management entity and host(s) supporting the particular logical entity.

Abstract: Example methods and systems for routing domain computation are described. In one example, a computer system may assign multiple logical entities with respective routing domain identifiers (IDs) by processing network topology information using multiple compute nodes. In response to detecting a network topology change associated with a particular logical entity, the computer system may determine first state change information identifying a first update to first state information maintained by a first compute node; and second state change information identifying a second update to second state information maintained by a second compute node. Further, the particular logical entity with an updated routing domain ID based on the first state change information and the second state change information. The updated routing domain ID may be used in a communication between a management entity and host(s) supporting the particular logical entity.

Abstract: This disclosure concerns the co-design of a testbench (100) and driver (102) of a device. It is an advantage in at least some embodiments that it improves driver reliability and reduces development cost. It does this by re-using the device functional layer (70) that is dependent on the device class but independent of the specific device and specific operating system (OS) of the driver. The device functional layer (70) is re-used as it is implemented in the device's testbench (100) and also as the core part of the device (driver (102). A scenario layer (68) is also used that is able to test the generic device interface (72) and device functional layer (70) in the testbench (100) environment, and the testing includes testing for responses to OS requests. This helps provide more exhaustive testing.

Abstract: This disclosure concerns the co-design of a testbench (100) and driver (102) of a device. It is an advantage in at least some embodiments that it improves driver reliability and reduces development cost. It does this by re-using the device functional layer (70) that is dependent on the device class but independent of the specific device and specific operating system (OS) of the driver. The device functional layer (70) is re-used as it is implemented in the device's testbench (100) and also as the core part of the device (driver (102). A scenario layer (68) is also used that is able to test the generic device interface (72) and device functional layer (70) in the testbench (100) environment, and the testing includes testing for responses to OS requests. This helps provide more exhaustive testing.