Abstract: A synchronization queuing service associated with a content management system repository can record file events occurring to content items maintained at the content management system repository. The synchronization queuing service can receive a file synchronization request for information identifying a content item to which a client machine is subscribed. The synchronization queuing service can determine consistency or inconsistency of a client machine state of the content item relative to the content item at the content management system repository and can respond to client machine with a file event summary comprising information usable by the client machine to identify actions necessary to synchronize the client machine state of the content item the content item.

Abstract: Content transformations can include transformation of content items in a CMS repository from a source format to a target format. Such transformations can be performed using a transformation node cluster having multiple nodes, each of which is configured for a specific content transformation type. Router nodes can receive requests for content items and route content items to transformation nodes having a proper content transformation type to either transform a requested content item to the target format or perform an intermediate transformation as part of a transformation chain. A transformation node cluster can be dynamically configurable based on estimates of expected loads for the various types of transformations. Systems, methods, and articles of manufacture are also described.

Abstract: A synchronization queuing service associated with a content management system repository can record file events occurring to content items maintained at the content management system repository. The synchronization queuing service can receive a file synchronization request for information identifying a content item to which a client machine is subscribed. The synchronization queuing service can determine consistency or inconsistency of a client machine state of the content item relative to the content item at the content management system repository and can respond to client machine with a file event summary comprising information usable by the client machine to identify actions necessary to synchronize the client machine state of the content item the content item.

Abstract: A workflow executed by an on-premise installation of the content management system can include a cloud workflow and an on-premise workflow relating to on-premise content retained in an on-premise repository managed by the on-premise installation of the content management system. A synchronization can be initiated between the on-premise content and a cloud copy of the on-premise content to reflect a change to either of the on-premise content or the cloud copy in the other of the on-premise content and the cloud copy. The cloud copy can exist at a location managed by a cloud-based installation of the content management system. Upon detection that the cloud workflow has been completed by the location using the cloud copy, a resumption of the on-premise workflow can be triggered using the synchronization between the on-premise content and the cloud copy of the on-premise content. Related systems, methods, products, etc. are described.