Abstract: Techniques for message indexing are described. In one embodiment, an apparatus may comprise a client front-end component operative to receive an incoming message from a client device at a client front-end component for a messaging system; and extract a message identifier for the incoming message from the incoming message, wherein the message identifier uniquely identifies the incoming message; and a message queue operative to store the incoming message in a message storage system based on indexing the incoming message based on the message identifier. Other embodiments are described and claimed.

Abstract: The disclosure is directed to pushing data updates to client computing devices (“clients”) in real-time. Clients can obtain data from a data storage layer by sending queries to the data storage layer that will return data compatible with the client's local data model. These queries are stored in a database and the identifier for the query (“query ID”) is used instead of the query itself. In the query stored in the database, a marker is used as a proxy for a content ID of the content to be retrieved. When querying, both the query ID and the content ID are passed to the data storage layer. The query stored with the query id is loaded, the marker is substituted with the content ID, and then executed.

Abstract: The disclosure is directed to pushing data updates to client computing devices (“clients”) in real-time. Clients can obtain data from a data storage layer by sending queries to the data storage layer that will return data compatible with the client's local data model. These queries are stored in a database and the identifier for the query (“query ID”) is used instead of the query itself. In the query stored in the database, a marker is used as a proxy for a content ID of the content to be retrieved. When querying, both the query ID and the content ID are passed to the data storage layer. The query stored with the query id is loaded, the marker is substituted with the content ID, and then executed.