Abstract: A method is provided for detecting irregularities of one or more application programmer interface (API) entities. The method includes receiving a request for data of one or more API entities. The method further includes monitoring said data from at least one server and detecting irregularities in the data. The method also includes displaying information pertaining to the irregularities to a user.

Abstract: Performing cache invalidation is disclosed, including: receiving an invalidation request to invalidate one or more invalidated cache entries of a cache storage, wherein the cache storage is configured to store cache entries; storing the invalidation request to invalidate the one or more invalidated cache entries in an invalidation data structure; prior to removing the one or more invalidated cache entries from the cache storage, receiving a data retrieval request for a requested cache entry from the cache storage; and using the invalidation data structure to determine whether the requested cache entry has been invalidated.

Abstract: Synchronization of transactional data and analytical data between data centers. Metadata is received by a transactional system from a user interface included in a customer data center. The metadata is then forwarded from the customer data center to an analytical system in a master data center. Data is forwarded from the customer data center to the master data center, the data being encrypted with a key uniquely associated with a customer. Role creation calls to create roles for one or more users associated with the customer data center are subsequently detected. The role creation calls crossing a data center boundary are further masqueraded.

Abstract: A method is provided for monitoring and reporting data of one or more application programmer interface (API) entities. The method includes receiving a request for usage data of one or more API entities. The method further includes monitoring said usage data from at least one server. The method also includes displaying information pertaining to said monitored usage data.

Abstract: A method is provided for detecting irregularities of one or more application programmer interface (API) entities. The method includes receiving a request for data of one or more API entities. The method further includes monitoring said data from at least one server and detecting irregularities in the data. The method also includes displaying information pertaining to the irregularities to a user.

Abstract: Lockless distributed counting of message requests. A plurality of message requests is received from a client by a plurality of message processors. A local count, for one time slot, is incremented in each message processor of the plurality of message processors based on the plurality of message requests. A global count in a shared state system, for one version, is incremented by value of the local count at a preconfigured time interval, the local count being decremented to a value zero. A global count in each message processor of the plurality of message processors is then synchronized, asynchronously, with the global count in the shared state system. The local count and the global count are subsequently reset in each message processor of the plurality of message processors to the value zero for a next time slot.

Abstract: A method and system for processing application programming interface (API) traffic includes determining corresponding API traffic at a time interval, assigning a corresponding priority value and allocating a cache memory to store a data set that corresponds to a high priority value. The method also includes receiving a plurality of sets of API requests, comparing corresponding precedence value associated with the sets of API requests, determining a set of API requests and allocating bandwidth to the set of API requests. The method further includes receiving a first set of API requests, determining a total number of processed API requests and predicting a second constant number API requests that is included in a second set of API requests. The system includes an electronic device, a communication interface, a memory and a processor.

Abstract: Synchronization of transactional data and analytical data between data centers. Metadata is received by a transactional system from a user interface included in a customer data center. The metadata is then forwarded from the customer data center to an analytical system in a master data center. Data is forwarded from the customer data center to the master data center, the data being encrypted with a key uniquely associated with a customer. Role creation calls to create roles for one or more users associated with the customer data center are subsequently detected. The role creation calls crossing a data center boundary are further masqueraded.

Abstract: Flow and module level debugging in a system. An applicable filter-set comprising at least one user defined flow and at least one module corresponding to the at least one user defined flow are identified. An incoming message flow is then tagged with information of the applicable filter-set. Further, the at least one module is detected for debugging corresponding to the user defined flow based on the tagged information of the incoming message flow. Log statements are then generated for the at least one module detected for debugging.