Abstract: A method, system, and computer readable storage to implement a data marketplace which stored data assets, such as tables, models, variables, etc. All of the data assets (assets) can be searched and retrieved from the data marketplace notwithstanding that the assets can be stored at different locations, in different forms, and in different platforms through an entire big data system. The data marketplace also predicts and suggests assets which will be likely to be relevant to a user's current project.

Abstract: Methods, systems, and non-transitory computer-readable media for evaluating changes to one or more advertising campaigns of an advertiser. In one aspect, advertising campaign modification data, specifying advertising campaign changes, is received from a campaign modification data source. A queue of changes based on the advertising campaign modification data is generated, and the changes from the queue are evaluated. It is determined whether to apply the changes to the advertising campaign based on results of the evaluating step and rule data specifying advertising campaign performance metrics and predefined performance metric values.

Abstract: A distributed data cache included in a content delivery network expedites retrieval of data for application execution by a server in a content delivery network. The distributed data cache is distributed across computer-readable storage media included in a plurality of servers in the content delivery network. When an application generates a query for data, a server in the content delivery network determines whether the distributed data cache includes data associated with the query. If data associated with the query is stored in the distributed data cache, the data is retrieved from the distributed data cache. If the distributed data cache does not include data associated with the query, the data is retrieved from a database and the query and associated data are stored in the distributed data cache to expedite subsequent retrieval of the data when the application issues the same query.

Abstract: Round-trip time (RTT) for communication between an edge point of presence (POP) in a content delivery network (CDN) and a local domain name server (LDNS) is determined by resolution of a canonical name (CNAME) record. A first server in a first edge POP in a CDN receives a request to resolve a domain name from a LDNS and transmits a CNAME record including a timestamp indicating when the CNAME record was transmitted to the LDNS. The first server subsequently receives a request from the LDNS to resolve the CNAME record and determines a RTT time indicating the time needed for round-trip transmission between the LDNS and the first server based on the time when the request to resolve the CNAME request was received by the first server and the time indicated by the timestamp.

Abstract: Round-trip time (RTT) for communication between an edge point of presence (POP) in a content delivery network (CDN) and a local domain name server (LDNS) is determined by resolution of a canonical name (CNAME) record. A first server in a first edge POP in a CDN receives a request to resolve a domain name from a LDNS and transmits a CNAME record including a timestamp indicating when the CNAME record was transmitted to the LDNS. The first server subsequently receives a request from the LDNS to resolve the CNAME record and determines a RTT time indicating the time needed for round-trip transmission between the LDNS and the first server based on the time when the request to resolve the CNAME request was received by the first server and the time indicated by the timestamp.

Abstract: A distributed data cache included in a content delivery network expedites retrieval of data for application execution by a server in a content delivery network. The distributed data cache is distributed across computer-readable storage media included in a plurality of servers in the content delivery network. When an application generates a query for data, a server in the content delivery network determines whether the distributed data cache includes data associated with the query. If data associated with the query is stored in the distributed data cache, the data is retrieved from the distributed data cache. If the distributed data cache does not include data associated with the query, the data is retrieved from a database and the query and associated data are stored in the distributed data cache to expedite subsequent retrieval of the data when the application issues the same query.

Abstract: Techniques are described for managing content by identifying content that has attributes of interest (e.g., content that is useful, humorous and/or that otherwise has a sufficiently high degree of quality) and by determining how to use such identified content. In some situations, a piece of content is automatically assessed in a manner based on automatically assessed levels of trust in users who are associated with the content, such as a user who authored or otherwise supplied the content and/or users who evaluated the content. For example, an automatically assessed level of trust for a user may be based on prior activities of the user and be used to predict future behavior of the user as a supplier of acceptable content and/or as an acceptable evaluator of supplied content, such as based on prior activities of the user that are not related to supplying and/or evaluating content.

Abstract: Techniques are described for enhancing the reliability of information received from users in various ways, such as by analyzing votes or other ratings supplied by a user in order to identify fraudulent and other unreliable ratings. Such analysis may be based at least in part on prior ratings submitted by the user, such as based on one or more patterns indicating that the user has a bias for or against one or more of various aspects. Unreliable ratings can then be excluded from use in various ways. This abstract is provided to comply with the rules requiring it, and is submitted with the intention that it not limit the scope of the claims.