Abstract: A system, method, and apparatus are provided for visualizing quotas on resources within a computing environment (e.g., a data center, a computing cluster) that includes multiple brokers, gateway servers, or other entities that control access to the resource(s). Through a visualization interface, an operator of a quota system can set, change, and/or delete quotas on resources and/or sub-resources for any number of clients or consumers of the resources. The visualization interface may also enable access to a log of changes to quotas and/or graphs or other displays of statuses of any selected quotas for any selected clients and resources/sub-resources.

Abstract: A system, method, and apparatus are provided for visualizing quotas on resources within a computing environment (e.g., a data center, a computing cluster) that includes multiple brokers, gateway servers, or other entities that control access to the resource(s). Through a visualization interface, an operator of a quota system can set, change, and/or delete quotas on resources and/or sub-resources for any number of clients or consumers of the resources. The visualization interface may also enable access to a log of changes to quotas and/or graphs or other displays of statuses of any selected quotas for any selected clients and resources/sub-resources.

Abstract: A system, method, and apparatus are provided for locally enforcing quotas on resources within a computing environment (e.g., a data center, a computing cluster) that includes multiple brokers, gateway servers, or other entities that control access to the resource(s). Instead of using global access statistics provided by all gateways, each server individually allows or denies requested access to a resource based on whether the requesting client has already exceeded its quota (or would exceed its quota if the request is approved). A client associated with a given call to a resource may be identified using a tuple formed from identifiers of multiple services in the call stack, such as a first service (e.g., a front-end or user-facing service) and an immediate service (e.g., a final service in the stack prior to receipt of the call at a gateway, broker, or other entity that manages access to the controlled resources).

Abstract: In order to request desired information from a graph database, a system executes a query against the graph database. The graph database may store a graph that includes nodes, edges between the nodes, and predicates to represent and store data with index-free adjacency. Moreover, the query may identify a first edge associated with a predicate that specifies one or more of the nodes in the graph. In response to the query, the system receives a result that includes a subset of the graph. In particular, the subset of the graph may include the desired information expressed within an associated structure of the graph.