Abstract: A method, comprising: receiving, at a computing system, a given single-action API call, the given single-action API call being transmitted by a sender, the given single-action API call being associated with a given operation; detecting whether the given single-action API call is part of a burst, wherein detecting whether the given single-action API call is part of the burst includes detecting whether a plurality of single-action API calls that are associated with the given operation have been received from the sender of the given single-action API call in a predetermined time window; when the given single-action API call is part of a burst, generating an error message in response to the given single-action API call and returning the error message to the sender of the given single-action API call; and when the given single-action API call is not part of a burst, executing the given single-action API call.

Abstract: An example methodology includes, responsive to receiving a first volume creation request to create one or more volumes on a storage device, creating a first operation object for the first volume creation request and determining that a waiting buffer is appropriate for the first operation object. The method also includes placing the first operation object in the waiting buffer and, responsive to a determination that the first operation object is a first operation object placed in the waiting buffer, notifying a waiting buffer thread of the first operation object in the waiting buffer. The method further includes, upon expiration of a predetermined buffer waiting period defined for the waiting buffer, by the waiting buffer thread, extracting the first volume creation request and a second volume creation request from the waiting buffer, combining the first and second operation objects into single workload, and executing the single workload.

Abstract: According to one aspect, a method includes: receiving a request by an application programming interface (API) of a server device, wherein servicing of the request involves use of one or more resources external to the server; determining, by a filter of the server device, a type of the request; sending, by the filter, the request to a controller selected from a plurality of controllers of the server device based on the request type, where different ones of the plurality of controllers are configured to service different types of API requests; and determining, by the controller, how to handle the request based at least in part upon a rate of recent request traffic received by the controller.

Abstract: A method comprising: receiving, at a management application, a first definition of a control window, the first definition specifying the control window in a local time of a time zone where the management application is being executed, wherein the first definition identifies: (i) a first start time for the control window, (ii) a first end time for the control window, and (iii) one or more days of the week when the control window should be enforced; detecting an applicable time in the time zone, the applicable time being one of standard time or daylight savings time; generating a second definition of the control window that corresponds to the applicable time, the second definition specifying the control window in a standardized time format, the second definition being generated based on the first definition; and causing the control window to be enforced in a storage array in accordance with the second definition.

Abstract: Techniques for performing management operations may include: creating a job using a graphical user interface (GUI) of an application, wherein the job includes at least one task and the job performs a first management operation including the at least one task; storing first information that describes the job in an application database for the application; and performing first processing that generates a code module for the job, wherein said first processing uses the first information from the application database. The code module may be a script written in a target script language. Multiple providers may converts different types of tasks to scripts. The providers may register prior to performing the first processing. Registering may include each provider declaring each type of task the provider converts to a specified target scripting language. The task types may be organized in a hierarchy of classes or categories.

Abstract: Techniques for performing management operations may include: creating a job using a graphical user interface (GUI) of an application, wherein the job includes at least one task and the job performs a first management operation including the at least one task; storing first information that describes the job in an application database for the application; and performing first processing that generates a code module for the job, wherein said first processing uses the first information from the application database. The code module may be a script written in a target script language. Multiple providers may converts different types of tasks to scripts. The providers may register prior to performing the first processing. Registering may include each provider declaring each type of task the provider converts to a specified target scripting language. The task types may be organized in a hierarchy of classes or categories.

Abstract: Techniques are provided for providing a type-based message bus with message type hierarchies for non-object oriented languages. In an example, a type-aware message bus receives a subscription message from a subscriber that identifies an object-oriented class. The message bus determines an event channel that corresponds to the class, and subscribes the subscriber to the event channel. The message bus also determines any event channels that correspond to a subclass of the class, and subscribes the subscriber to those event channels. When a publisher publishes a message to an event channel, the message bus publishes the message to each subscriber of the event channel, which can have the effect of publishing the message to subscribers that originally subscribed to superclass event channels of the event channel.

Abstract: Techniques are provided for providing a type-based message bus with message type hierarchies for non-object oriented languages. In an example, a type-aware message bus receives a subscription message from a subscriber that identifies an object-oriented class. The message bus determines an event channel that corresponds to the class, and subscribes the subscriber to the event channel. The message bus also determines any event channels that correspond to a subclass of the class, and subscribes the subscriber to those event channels. When a publisher publishes a message to an event channel, the message bus publishes the message to each subscriber of the event channel, which can have the effect of publishing the message to subscribers that originally subscribed to superclass event channels of the event channel.