Abstract: At a logging service, a representation of a transaction requested by a client is received. The transaction includes at least a first write operation directed to a data object at a first data store. Based at least in part on the contents of the representation and contents of a persistent log of the logging service, a determination is made that the requested transaction is to be committed. A log record corresponding to the first write operation is inserted into the persistent log. The first write is propagated to the first data store after the record has been inserted in the persistent log.

Abstract: Systems and methods are disclosed to implement a real-time data validation system that prevents problematic updates from being replicated from a primary database to a replica database. In embodiments, the data validation system injects a time delay into the replication process, so that when an update in a replication stream fails a specified data validation, the data validation system will prevent the update from being applied to the replica. In embodiments, the replication process is halted, a snapshot of the replica database is taken during the halt, and replication to the replica is resumed. Accordingly, if the problematic update is later confirmed to be invalid, the replica database can be rolled back to a point before the problematic update. Advantageously, the disclosed system can be used to implement a variety of data validations on top of a database replication process to protect the replica database from receiving undesired updates.

Abstract: The present disclosure describes a telecommunications structure. The telecommunications structure includes an antenna frame including a plurality of horizontal members and a plurality of vertical members mounted on the horizontal members, wherein one or more of the vertical members are formed of a fiber-reinforced polymer and at least one piece of telecommunications equipment mounted on one of the fiber-reinforced polymer vertical members. Assemblies including passive intermodulation reducing mechanical connections are also described herein.

Abstract: A railcar diaphragm includes a car side assembly configured to be coupled to an end wall of a railcar, a wear side assembly configured to engage the wear side assembly of another railcar diaphragm or an other railcar when the other railcar is coupled to the railcar, a bellows assembly disposed between the car side assembly and the wear side assembly to provide a pathway and at least one elastomer suspension unit assembly including an elastomer suspension unit, a bearing assembly and an arm having a first end coupled to the elastomer suspension unit and a second end coupled to the bearing assembly. The elastomer suspension unit assembly is coupled to the car side or wear side assembly via the bearing assembly. The arm is biased towards an initial position by the elastomer suspension unit as a distance between the car side assembly and the wear side assembly changes.

Abstract: Techniques are described for optimizing the allocation of computing resources provided by a service provider network—for example, compute resources such as virtual machine (VM) instances, containers, standalone servers, and possibly other types of computing resources—among computing workloads associated with a user or group of users of the service provider network. A service provider network provides various tools and interfaces to help businesses and other organizations optimize the utilization of computing resource pools obtained by the organizations from the service provider network, including the ability to efficiently schedule use of the resources among workloads having varying resource demands, usage patterns, relative priorities, execution deadlines, or combinations thereof. A service provider network further provides various graphical user interfaces (GUIs) to help users visualize and manage the historical and scheduled uses of computing resources by users' workloads according to user preferences.

Abstract: Techniques are described for optimizing the allocation of computing resources provided by a service provider network—for example, compute resources such as virtual machine (VM) instances, containers, standalone servers, and possibly other types of computing resources—among computing workloads associated with a user or group of users of the service provider network. A service provider network provides various tools and interfaces to help businesses and other organizations optimize the utilization of computing resource pools obtained by the organizations from the service provider network, including the ability to efficiently schedule use of the resources among workloads having varying resource demands, usage patterns, relative priorities, execution deadlines, or combinations thereof. A service provider network further provides various graphical user interfaces (GUIs) to help users visualize and manage the historical and scheduled uses of computing resources by users' workloads according to user preferences.

Abstract: Techniques are described for optimizing the allocation of computing resources provided by a service provider network—for example, compute resources such as virtual machine (VM) instances, containers, standalone servers, and possibly other types of computing resources—among computing workloads associated with a user or group of users of the service provider network. A service provider network provides various tools and interfaces to help businesses and other organizations optimize the utilization of computing resource pools obtained by the organizations from the service provider network, including the ability to efficiently schedule use of the resources among workloads having varying resource demands, usage patterns, relative priorities, execution deadlines, or combinations thereof. A service provider network further provides various graphical user interfaces (GUIs) to help users visualize and manage the historical and scheduled uses of computing resources by users' workloads according to user preferences.

Abstract: A high-availability (HA) framework for services deployed in provider network environments. Services may be deployed as machine images or containers to a provider network. The HA framework provides a “wrapper” around the deployed services that provides feedback loops and flow control for inbound and outbound communications to other services on the provider network or to other external entities. The HA framework intercepts inbound and outbound traffic to the service, and may automatically determine, configure, and adjust networking management aspects such as timeouts, flow control, etc. for the service. The HA framework may also intercept outbound traffic to monitor outbound connections to other services to determine if the services satisfy HA requirements of the service.

Abstract: Generally described, one or more aspects of the present application relate to deploying a software update to multiple clusters in a decentralized manner, where the individual clusters manage their own deployments based on successes and/or failures experienced by other clusters that have installed the software update. For example, a set of least conservative clusters may install the software update right away, whereas a set of more conservative clusters may wait and see how many of the clusters have installed the update so far and/or how the update is performing on those clusters, before installing the update themselves.

Abstract: Techniques for an optimization service of a service provider network to generate an architecture diagram that represents an architecture of a web-based application. The optimization service may use the architecture diagram to determine modifications or changes to make to the application. For example, the optimization service may compare the architecture diagram with optimized architecture diagrams that represent application best practices, and determine the modifications or change to make to the application to optimize the application and bring the application in-line with best practices. Further, the optimization service may use the architecture diagram to generate a visualization, and provide the user account with the visualization of the architecture diagram to show users their application architecture.

Abstract: A computing resource service provider provides computing resources to customers, for example, computer system instances supported by server computer systems. These computer system instances may include logical volumes to support execution of the computer system instance. In addition, these instances may be terminated from time to time for various reasons. A stop signal transmitted to computing resource supporting a particular computer system instance may indicate that the particular computer system instance is to be terminated. In response to termination, the particular computer system instance may operate in accordance to a particular behavior.

Abstract: Techniques are described for providing a multi-service storage layer in a cloud provider network for applications and workloads that are highly sensitive to outages affecting “mission critical” data or other resources. A multi-service storage layer is designed to provide additional resiliency against various types of correlated failures among existing geographic regions by enabling the storage of data using a plurality of separate storage services and storage resource types and across a plurality of regions of the cloud-provider network. A multi-service storage layer provides an application programming interface (API) with actions for storing, retrieving, and querying data stored in a highly available storage resource across a selection of underlying storage services.

Abstract: The present disclosure describes strand mounts for small cell radios and/or antennas. A strand mount may include a plurality of polymeric mounting tubes configured such that one or more small cell radios and/or antennas can be mounted thereto, a pair of polymeric retaining members, each retaining member having a plurality of apertures sized and configured to receive a corresponding end of each mounting tube, and one or more mounting brackets configured to secure the strand mount on a cable strand. Stand mount assemblies are also described herein.

Abstract: Techniques are described for enabling users to create reservations for compute capacity at a service provider network intended for use in disaster recovery scenarios. A service provider can use separate geographic areas (sometimes referred to as “regions” or “availability zones”) defined by the service provider network to enable users to share reservations of compute capacity intended for use in disaster recovery scenarios. A disaster recovery launch reservation (DRLR) is a reservation of a given unit of compute capacity that is unique to a source geographic area (that is, a defined area of the service provider network containing computing resource(s) for which a user desires to obtain backup compute capacity) and a destination area (that is, a defined area of the service provider network at which the reserved compute capacity is located), where other users can reserve the compute capacity relative to other source geographic area-to-destination geographic area mappings.

Abstract: Techniques are described for enabling customers of a service provider network to modify and extend the functionality of application programming interfaces (APIs) provided to customers by various services of the provider network. Services of a service provider network provide interfaces that enable customers and other users to define custom API actions representing functionality to be performed by the services upon receipt of corresponding API requests. In this manner, the functionality exposed by provider network services to customers via APIs becomes extensible and customizable to fit customers' particular use cases and without the provider network needing to contemplate and explicitly implement all possible customer-specific API action variations.

Abstract: A network-based service may schedule requests received from clients according to information regarding prior requests from the client included the requests. When a request is received at a network-based service, information regarding the request, and possibly other prior requests, may be included in response for the request sent to the client. The client may then include that information in a subsequent request to the network-based service. An evaluation of the information may determine a scheduling decision for the request and the request may then be processed according to the scheduling decision.

Abstract: A clock recovery circuit includes a first pulse circuit, a second pulse circuit, a state change circuit connected to the first pulse circuit and the second pulse circuit and a first delay circuit connected to the state change circuit and each of the first pulse circuit and the second pulse circuit. The first pulse circuit receives data inputs to generate a first pulse signal. The second pulse circuit receives the data inputs to generate a second pulse signal. The state change circuit receives the first pulse signal and the second pulse signal and generate a first clock signal for a first transition of one of the data inputs in a first unit interval (UI). The first delay circuit receives the generated first clock signal and mask other transitions of the data inputs in the first UI.

Abstract: A track-module apparatus comprising: (a) idler-arm axle structure for a vehicle and having leading and trailing idler-arm axles; (b) a leading idler arm rotatably attached to the leading idler-arm axle and extending forwardly to a leading-arm distal end at which a leading ground-engaging idler wheel is rotatably attached and rearwardly to a rearward suspension end; (c) a trailing idler arm rotatably attached to the trailing idler-arm axle and extending rearwardly to a trailing-arm distal end at which a trailing ground-engaging idler wheel is rotatably attached and forwardly to a forward suspension end; (d) bogie-axle structure (i) affixed to one of the idler arms, (ii) having at least one bogie-arm axle, and (iii) positioning the at least one bogie-arm axle adjacent to and below the idler-arm axle of the idler arm to which it is affixed; (e) leading-arm and trailing-arm suspension elements rotatably attached to and extending downwardly from the rearward and forward suspension ends, respectively, and each havi

Abstract: Techniques are described for enabling customers of a service provider network to modify and extend the functionality of application programming interfaces (APIs) provided to customers by various services of the provider network. Services of a service provider network provide interfaces that enable customers and other users to define custom API actions representing functionality to be performed by the services upon receipt of corresponding API requests. In this manner, the functionality exposed by provider network services to customers via APIs becomes extensible and customizable to fit customers' particular use cases and without the provider network needing to contemplate and explicitly implement all possible customer-specific API action variations.

Abstract: A railcar diaphragm includes a car side assembly configured to be coupled to an end wall of a railcar, a wear side assembly configured to engage the wear side assembly of another railcar diaphragm or an other railcar when the other railcar is coupled to the railcar, a bellows assembly disposed between the car side assembly and the wear side assembly to provide a pathway and at least one elastomer suspension unit assembly including an elastomer suspension unit, a bearing assembly and an arm having a first end coupled to the elastomer suspension unit and a second end coupled to the bearing assembly. The elastomer suspension unit assembly is coupled to the car side or wear side assembly via the bearing assembly. The arm is biased towards an initial position by the elastomer suspension unit as a distance between the car side assembly and the wear side assembly changes.