Abstract: Aspects define a dynamic threshold filter data structure that includes a pairing of an override log level value to a key value; in response to an incoming processing request, identify a user identification value that is linked to the request, wherein the user identification value is associated to a default logging level within a thread context map for logging data associated with executing processes in satisfaction of the processing request, and wherein the default logging level is different from the override log level; and in response to determining that the user identification value matches the key value, log data associated with executing processes in satisfaction of the processing request to the override log level.

Abstract: A system, method implemented on a computer system, and computer program product for exchanging shared data. A consumer of shared data receives new shared data and determines whether the new shared data comprises a breaking change. In response to a determination that the new shared data does not comprise a breaking change, the new shared data is saved and set as the current shared data. In response to a determination that the new shared data does comprise a breaking change, the new shared data is saved but is not set as the current shared data. New shared data that was saved but not set as current shared data may be set as current shared data during deployment of new program code for the consumer.

Abstract: Aspects refresh permission credentials by populating within user profile data sets cached for members an invalidated value and a first timestamp of said populating the invalidated value; selecting user profile data sets including the invalidated value; identifying a second timestamp of time of creation of the permission credential within the selected user profile data sets; and in response to determining that a time elapsed between the first and second timestamps does not exceed a threshold, rebuilding the selected user profile data sets to include an updated value of the permission credential and set the second timestamp value to a current time of the rebuild, and cache (store) the rebuilt selected user profile data set within the repository.

Abstract: Aspects store configuration version data for an application into a shared cache in a structured data format; in response to a request at run-time for the configuration version data, determine whether run-time format data of the configuration version data is stored in a different, local cache; and in response to determining that the run-time format configuration version data is not stored in the local cache, during execution of the application, read the structured data format data from the shared cache, translate the read data into the run-time data format, store the translated data into the local cache in the run-time format file and return the configuration version run-time format data stored within the local cache in satisfaction of the request at run-time for the configuration version data of the application.

Abstract: In response to determining that an application programming interface call made in response to a first request for the call has failed and that no fail entry has been set for the call, aspects increment a fail count value and set a fail entry for the call that includes a fail response generated by the failure of the call; in response to determining that the call has failed in response to a subsequent, second request for the call, determine whether the incremented fail count value meets a limit value, and if so, set a paused timestamp value for the fail entry; and in response to additional requests for the call occurring within a pause period of time from the paused timestamp value, pause making the call and return the fail entry set for the call in satisfaction of said additional requests.

Abstract: Aspects subscribe consumer message threads to each of a plurality of topics including a high-priority topic and a different, low-priority topic; initialize both the high-priority and low-priority topics as not-paused; poll for an unread message from not-paused ones of the high-priority and low-priority topics; in response to a return of an unread message from polling the not-paused ones of the high-priority and low-priority topics, pause the low-priority topic and process the returned unread message; and, until determining that no new message is returned, iteratively repoll for new unread messages from not-paused ones of the high-priority and low-priority topics and process any new unread messages returned from each repolling, wherein the low-priority topic is paused during each repolling executed prior to determining that no new message is returned from the repolling.

Abstract: In response to determining that an application programming interface call made in response to a first request for the call has failed and that no fail entry has been set for the call, aspects increment a fail count value and set a fail entry for the call that includes a fail response generated by the failure of the call; in response to determining that the call has failed in response to a subsequent, second request for the call, determine whether the incremented fail count value meets a limit value, and if so, set a paused timestamp value for the fail entry; and in response to additional requests for the call occurring within a pause period of time from the paused timestamp value, pause making the call and return the fail entry set for the call in satisfaction of said additional requests.

Abstract: Aspects define a dynamic threshold filter data structure that includes a pairing of an override log level value to a key value; in response to an incoming processing request, identify a user identification value that is linked to the request, wherein the user identification value is associated to a default logging level within a thread context map for logging data associated with executing processes in satisfaction of the processing request, and wherein the default logging level is different from the override log level; and in response to determining that the user identification value matches the key value, log data associated with executing processes in satisfaction of the processing request to the override log level.

Abstract: Aspects subscribe consumer message threads to each of a plurality of topics including a high-priority topic and a different, low-priority topic; initialize both the high-priority and low-priority topics as not-paused; poll for an unread message from not-paused ones of the high-priority and low-priority topics; in response to a return of an unread message from polling the not-paused ones of the high-priority and low-priority topics, pause the low-priority topic and process the returned unread message; and, until determining that no new message is returned, iteratively repoll for new unread messages from not-paused ones of the high-priority and low-priority topics and process any new unread messages returned from each repolling, wherein the low-priority topic is paused during each repolling executed prior to determining that no new message is returned from the repolling.

Abstract: Aspects store configuration version data for an application into a shared cache in a structured data format; in response to a request at run-time for the configuration version data, determine whether run-time format data of the configuration version data is stored in a different, local cache; and in response to determining that the run-time format configuration version data is not stored in the local cache, during execution of the application, read the structured data format data from the shared cache, translate the read data into the run-time data format, store the translated data into the local cache in the run-time format file and return the configuration version run-time format data stored within the local cache in satisfaction of the request at run-time for the configuration version data of the application.

Abstract: Aspects refresh permission credentials by populating within user profile data sets cached for members an invalidated value and a first timestamp of said populating the invalidated value; selecting user profile data sets including the invalidated value; identifying a second timestamp of time of creation of the permission credential within the selected user profile data sets; and in response to determining that a time elapsed between the first and second timestamps does not exceed a threshold, rebuilding the selected user profile data sets to include an updated value of the permission credential and set the second timestamp value to a current time of the rebuild, and cache (store) the rebuilt selected user profile data set within the repository.