Abstract: Techniques for intelligent messaging for message syncing are described. An apparatus may comprise a recipient inbound messaging component, a recipient queue management component, a recipient update customization component, and a recipient outbound messaging component. The recipient inbound messaging component may be operative to receive an incoming update at a recipient update queue, the recipient update queue associated with a recipient of the incoming update. The recipient queue management component may be operative to add the incoming update to the recipient update queue and determine a recipient messaging endpoint to receive the incoming update. The recipient update customization component may be operative to retrieve one or more recipient messaging endpoint parameters associated with the recipient messaging endpoint and generate a customized incoming update from the incoming update according to the one or more recipient messaging endpoint parameters.

Abstract: Techniques for data reads from secondary stores are described. In one embodiment, an apparatus may comprise a client front-end component of a messaging system operative to receive a messaging client update request from a client device; retrieve an up-to-date message set from a message cache component of the messaging system; and provide the up-to-date message set to the client device; and; the message cache component operative to retrieve a message set from a message store in response to the messaging client update request; determine that the message set is an out-of-date message set; retrieve a recent message update set from a message queue, the recent message update set comprising a plurality of message updates; and apply the plurality of message updates to the out-of-date message set to generate an up-to-date message set. Other embodiments are described and claimed.

Abstract: The disclosure is directed to moving an application, e.g., a messenger service in a social networking application, to various locations in a distributed computing system, e.g., to improve an efficiency of the application. For example, the application can be moved to a data center that is closer to a location of a user to decrease a latency associated with accessing the application. In another example, the application can be moved to a data center that is closer to a location of a storage system that stores data associated with the application to improve a throughput of the application, e.g., a rate at which data is read and/or written.

Abstract: Techniques for data reads from secondary stores are described. In one embodiment, an apparatus may comprise a client front-end component of a messaging system operative to receive a messaging client update request from a client device; retrieve an up-to-date message set from a message cache component of the messaging system; and provide the up-to-date message set to the client device; and; the message cache component operative to retrieve a message set from a message store in response to the messaging client update request; determine that the message set is an out-of-date message set; retrieve a recent message update set from a message queue, the recent message update set comprising a plurality of message updates; and apply the plurality of message updates to the out-of-date message set to generate an up-to-date message set. Other embodiments are described and claimed.

Abstract: The disclosure is directed to moving an application, e.g., a messenger service in a social networking application, to various locations in a distributed computing system, e.g., to improve an efficiency of the application. For example, the application can be moved to a data center that is closer to a location of a user to decrease a latency associated with accessing the application. In another example, the application can be moved to a data center that is closer to a location of a storage system that stores data associated with the application to improve a throughput of the application, e.g., a rate at which data is read and/or written.

Abstract: Various of the present embodiments present a network protocol facilitating intermediary analysis and modification of packets in a compressed data stream is provided. Particularly, a user specified header-payload architecture built using a Machine-to-Machine protocol, e.g., the Message Queueing Telemetry Transport (MQTT™) protocol, may be divided into a “header” and a “payload” portion. The payload may include, e.g., JSON data. Both the “header” and the “payload” portions may be serialized, but only the payload portion may be compressed. An intermediate computing device between the source computing device transmitting the stream and the destination computing device receiving the stream may receive the packet. The intermediate computing device may perform operations using the uncompressed “header”, such as substituting an identifier so as to chronicle the path traveled by the packet to the destination.

Abstract: Techniques for a sequential message reader for message syncing are described. An apparatus may comprise a network component and an inbox management component. The network component may be operative to receiving an incoming update at a messaging endpoint from a recipient update queue, the incoming update comprising an incoming recipient sequence number. The inbox management component may be operative to add the incoming update to a message inbox on the messaging endpoint, the incoming update added to the message inbox in an order determined by the incoming recipient sequence number and determine based on the incoming recipient sequence number whether one or more additional updates are missing from the message inbox on the messaging endpoint. Other embodiments are described and claimed.

Abstract: Techniques for intelligent messaging for message syncing are described. An apparatus may comprise a recipient inbound messaging component, a recipient queue management component, a recipient update customization component, and a recipient outbound messaging component. The recipient inbound messaging component may be operative to receive an incoming update at a recipient update queue, the recipient update queue associated with a recipient of the incoming update. The recipient queue management component may be operative to add the incoming update to the recipient update queue and determine a recipient messaging endpoint to receive the incoming update. The recipient update customization component may be operative to retrieve one or more recipient messaging endpoint parameters associated with the recipient messaging endpoint and generate a customized incoming update from the incoming update according to the one or more recipient messaging endpoint parameters.

Abstract: Techniques for a persistent queue for message syncing are described. A recipient inbound messaging component may receive an incoming update at a recipient update queue. A recipient queue management component may determine an incoming recipient sequence number for the recipient update queue. A recipient outbound messaging component may transmit the incoming update to the recipient messaging endpoint. Other embodiments are described and claimed.