Abstract: Techniques for assigning entities to data centers are provided. In one technique, usage data associated with a particular entity that is assigned to a first data center is generated. The usage data indicates activity of multiple users relative to the particular entity. It is determined, based on the usage data, whether the particular entity is to be assigned to another data center. If so, then the particular entity is assigned to a second data center.

Abstract: A machine may be configured to perform management of a lockdown of entity-related data in a database. For example, the machine identifies a replication lag trend associated with replicating data from a first data center to a second data center. The machine causes, based on the replication lag trend, a replication of data associated with a particular entity from a first record of the first data center to a second record of the second data center. The machine causes a lockdown, for a period of time, of the second record. The lockdown prevents servicing requests for data associated with the particular entity that are received from client devices associated with users related to the particular entity. The machine dynamically adjusts the period of time based on a monitoring of a completion of the replication. The machine causes a lifting of the lockdown based on the dynamically adjusted period of time.

Abstract: Techniques for assigning entities to data centers are provided. In one technique, usage data associated with a particular entity that is assigned to a first data center is generated. The usage data indicates activity of multiple users relative to the particular entity. It is determined, based on the usage data, whether the particular entity is to be assigned to another data center. If so, then the particular entity is assigned to a second data center.

Abstract: In some embodiments, the disclosed subject matter involves load balancing of application services usage in data centers based at least on entity status of the users. An entity routing system is used to proxy user requests to the selected data center to effect load balancing. The entity and usage data is monitored and analyzed. Entity routing data is modified to enable reassignment of data centers hosting an application service in use by the entity. Once a desired reassignment is identified, the entity routing database is updated with the new data center corresponding to the application service. User requests for the reassigned application service are then automatically routed to the new data center at the frontend. The user's entity status is defined by at least the application service requested, and may include the user's organization, geographic area and other criteria. Other embodiments are described and claimed.

Abstract: In some embodiments, the disclosed subject matter involves an entity routing service to route user requests for an application service to a particular data center based on the user's entity status. The user's entity status is defined by at least the application service requested, and may include the user's organization, geographic area and other criteria. The routing may be effected at the frontend application server level rather than at the backend. Other embodiments are described and claimed.

Abstract: A system, a machine-readable storage medium storing instructions, and a computer-implemented method as described herein are directed to a Sales Lead Engine that links external data to social network data from a social network service. The Sales Lead Engine determines the external data and the social network data satisfy a sales lead criterion. The Sales Lead Engine identifies an organization account in the social network service identified by the external data and the social network data. The Sales Lead Engine provides a sales lead notification to a target member account based on a selection by the target member account to follow the organization account in the social network service.

Abstract: A system, method, and apparatus for de-duplicating and serving a combined content feed are provided. The combined content includes items of two or more classes, such as sponsored and unsponsored, wherein some or all unsponsored content items may be sponsored. A feed service obtains sponsored and unsponsored items suitable for a user to whom the combined content feed is to be served. The service determines whether an item is duplicated among the multiple classes. If so, a distance between the duplicates is calculated (within the feed). If the distance is less than a first threshold, one of them is discarded and may or may not be replaced. A decision regarding which to eject may depend upon which version (e.g., sponsored or unsponsored) is positioned earlier in the feed, whether the duplicates are also less than a second threshold apart (which is lower than the first threshold), and/or other factors.

Abstract: In an example embodiment, information about one or more Customer Relationship Management (CRM) entities is received from a CRM system, the information including an identification of each of the one or more CRM entities and usage information about how a user interacted with each of the one or more CRM entities. Then, at a software tool distinct from the CRM system, one or more actionable insights related to the one or more CRM entities are identified. The relevance of the one or more actionable insights to the user is then determined based on the usage information. One or more of the one or more actionable insights are then presented to the user based on the determined relevance via the software tool.