Abstract: Methods, systems and computer program products are provided for prefetching based on historical use and real-time signals. Forecast models may be configured to forecast whether to prefetch information (e.g. keys responsive to queries) for future time intervals based on historical use and internal or external signals that may influence forecasts, such as prevailing conditions. Historical use of keys may be analyzed for patterns and trends with multiple seasonalities per category and/or per key. Time series data and forecasts may be indexed by cache categories and time intervals. Forecast models may be trainable, optimizable, configurable and/or auto-correcting on a per-category and/or a per-key basis. Forecast precision indicators, confidence indicators and configurable thresholds may be used to optimize performance. Operations may be distributed among multiple servers. Tasks may be time-distributed by offsets. Cached information may be assigned a time to live (TTL) independent of other cached information.

Abstract: Methods, systems and computer program products are provided for prefetching based on historical use and real-time signals. Forecast models may be configured to forecast whether to prefetch information (e.g. keys responsive to queries) for future time intervals based on historical use and internal or external signals that may influence forecasts, such as prevailing conditions. Historical use of keys may be analyzed for patterns and trends with multiple seasonalities per category and/or per key. Time series data and forecasts may be indexed by cache categories and time intervals. Forecast models may be trainable, optimizable, configurable and/or auto-correcting on a per-category and/or a per-key basis. Forecast precision indicators, confidence indicators and configurable thresholds may be used to optimize performance. Operations may be distributed among multiple servers. Tasks may be time-distributed by offsets. Cached information may be assigned a time to live (TTL) independent of other cached information.

Abstract: Network services may include data associated with one or more entities. An aggregator service may host respective application programming interfaces (APIs) of the services at a single endpoint of the network such that the entities, including associations and relationships between entities, may be federated. For example, the services may register the entities of which the data of each of the services is associated with through a declarative entity model to establish an API schema for each of the services, which may be published at the aggregator service. In response to receipt of a request for entity related data from a client, the aggregator service may employ the declarative entity model to determine which of the services are associated with the entity related data such that a query may be submitted to the services, and how to aggregate responses to the query received from the services for transmission to the client.

Abstract: An interface mechanism is provided for developers to bundle together a set of extensions (or add-ins) to a productivity suite allowing end users and system administrators to manage their lifecycle in a unified way. Aspects such as discovery, acquisition, authorization deployment, management, updates, and similar ones may be addressed for the bundle as opposed to each of the different extensions (for example extensions for different versions of the same application such as desktop version, web application version, mobile version, etc.). Bundles may also provide a means to match specific functional sets or commercial offerings to specific user or customer profiles.

Abstract: Network services may include data associated with one or more entities. An aggregator service may host respective application programming interfaces (APIs) of the services at a single endpoint of the network such that the entities, including associations and relationships between entities, may be federated. For example, the services may register the entities of which the data of each of the services is associated with through a declarative entity model to establish an API schema for each of the services, which may be published at the aggregator service. In response to receipt of a request for entity related data from a client, the aggregator service may employ the declarative entity model to determine which of the services are associated with the entity related data such that a query may be submitted to the services, and how to aggregate responses to the query received from the services for transmission to the client.

Abstract: An interface mechanism is provided for developers to bundle together a set of extensions (or add-ins) to a productivity suite allowing end users and system administrators to manage their lifecycle in a unified way. Aspects such as discovery, acquisition, authorization deployment, management, updates, and similar ones ma be addressed for the bundle as opposed to each of the different extensions (for example extensions for different versions of the same application such as desktop version, web application version, mobile version, etc.). Bundles may also provide a means to match specific functional sets or commercial offerings to specific user or customer profiles.