Abstract: Determining correct base container images to support custom container images is provided. A comparison between layers of a base container image corresponding to a current version of an operand and layers of a custom container image built by a user is performed using an operator. It is determined whether the user utilized a correct base container image to build the custom container image based on the comparison between the layers of the base container image corresponding to the current version of the operand and the layers of the custom container image built by the user. A runtime is generated in a cluster of host nodes to provide a service based on the custom container image in response to determining that the user utilized the correct base container image to build the custom container image.

Abstract: Determining correct base container images to support custom container images is provided. A comparison between layers of a base container image corresponding to a current version of an operand and layers of a custom container image built by a user is performed using an operator. It is determined whether the user utilized a correct base container image to build the custom container image based on the comparison between the layers of the base container image corresponding to the current version of the operand and the layers of the custom container image built by the user. A runtime is generated in a cluster of host nodes to provide a service based on the custom container image in response to determining that the user utilized the correct base container image to build the custom container image.

Abstract: Dynamically calculating and re-calculating priority values for a set of microservices that are deployed and run in a containerized environment. Before new priority values are assigned to the microservices, an initial default priority value is assigned to a microservice of interest. When the microservice of interest is deployed and run in the containerized environment, the generated telemetry data is used, in part, as a basis to determine a frequency in which any given microservice is being utilized, and more particularly, the microservice of interest. Based upon the determined frequency, a role for the microservice of interest can be inferred. As a result, this inferred role for the microservice of interest is used to dynamically assign a current priority value for the microservice of interest.

Abstract: Concepts for controlling interaction with scalable applications are presented. One example comprises associating metadata with an application interface specification of an application. Based on the metadata associated with the application interface specification of the application, configuration of shards for managing traffic of the interaction and/or integration with the application interface is controlled. Traffic is then routed to configured shards.

Abstract: A method, computer system, and computer program product for migrating a service (e.g. microservice) from using a first application programming interface version to using a second (e.g. newer or updated) application programming interface version. The method may include determining a difference between specifications of the first and second versions of the application programming interface. Historical usage of the first version of the application programming interface by the service may then be analyzed with respect to the difference so as to determine if the service meets the specification of the second version of the application programming interface. Responsive to determining the service meets the specification of the second version of the application programming interface difference, the service may be migrated from using the first version of the application programming interface to using the second version of the application programming interface.

Abstract: A method, computer system, and a computer program product for configuring application instances on scaling is provided. The present invention may include receiving a client request, wherein the client request includes one or more commands. The present invention may include determining whether the client request is to be acted on by all application instances based on a type of client request, wherein the type of client request is determined based on at least routing metadata in an application interface specification. The present invention may include determining the client request is be acted on by all application instances.

Abstract: A method, computer system, and a computer program product for coordinating requests actioned at a scalable application is provided. The present invention may include registering metadata regarding response behavior to be applied when actioning a client request to multiple application instances. The present invention may include augmenting a client request according to the metadata to provide augmented request instances to coordinate completion on a required number of response instances from the application instances to which the augmented request instances are routed. The present invention may include coordinating a status of the client request across the application instances to terminate outstanding augmented request instances when a required number of completed instances is received.

Abstract: A method, computer system, and a computer program product for coordinating requests actioned at a scalable application is provided. The present invention may include registering metadata regarding response behavior to be applied when actioning a client request to multiple application instances. The present invention may include augmenting a client request according to the metadata to provide augmented request instances to coordinate completion on a required number of response instances from the application instances to which the augmented request instances are routed. The present invention may include coordinating a status of the client request across the application instances to terminate outstanding augmented request instances when a required number of completed instances is received.

Abstract: Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for receiving, from a client device, a first notification of an ad space from a seller, identifying ad conditions corresponding to an ad space inventory to which the ad space belongs comprising a first condition that identifies an allowed creative media type for the ad space inventory, sending a second notification requesting a bid on the ad space to bidders, each bidder representing a respective buyer, receiving bids from the bidders, each bid corresponding to a respective bid price, buyer, and a creative, determining that a first bid of the bids corresponds to a first creative having a media type different from the allowed creative media type, and identifying a preexisting arrangement between the buyer corresponding to the first bid and the seller and, based thereon, allowing the first creative to be served to the ad space.

Abstract: Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for receiving, from a client device, a first notification of an ad space from a seller, identifying ad conditions corresponding to an ad space inventory to which the ad space belongs comprising a first condition that identifies an allowed creative media type for the ad space inventory, sending a second notification requesting a bid on the ad space to bidders, each bidder representing a respective buyer, receiving bids from the bidders, each bid corresponding to a respective bid price, buyer, and a creative, determining that a first bid of the bids corresponds to a first creative having a media type different from the allowed creative media type, and identifying a preexisting arrangement between the buyer corresponding to the first bid and the seller and, based thereon, allowing the first creative to be served to the ad space.

Abstract: Concepts for controlling interaction with a scalable application are presented. An example includes registering an interface specification to an application, wherein metadata is associated with the interface specification. The method then includes routing a request to instances of the application based on the metadata associated with the interface specification for the application, then combining one or more responses from the instances of the application to form an aggregate response based on the metadata associated with the interface specification for the application.

Abstract: Concepts for controlling interaction with a scalable application are presented. An example includes registering an interface specification to an application, wherein metadata is associated with the interface specification. The method then includes routing a request to instances of the application based on the metadata associated with the interface specification for the application, then combining one or more responses from the instances of the application to form an aggregate response based on the metadata associated with the interface specification for the application.

Abstract: A method, computer system, and computer program product for migrating a service (e.g. microservice) from using a first application programming interface version to using a second (e.g. newer or updated) application programming interface version. The method may include determining a difference between specifications of the first and second versions of the application programming interface. Historical usage of the first version of the application programming interface by the service may then be analyzed with respect to the difference so as to determine if the service meets the specification of the second version of the application programming interface. Responsive to determining the service meets the specification of the second version of the application programming interface difference, the service may be migrated from using the first version of the application programming interface to using the second version of the application programming interface.

Abstract: The present invention relates to a flashlight capable of generating and projecting multiple colors within one flashlight unit where said flashlight contains an extendable lens, a light source, a moveable member positionable at various locations to be moved across said light source, a rechargeable power source and a tail cap switch for ‘on’ and ‘off’ functions as well as dimming and brightening of a light source beam. The moveable member is slidably fixed to move perpendicular to a light source whereby movement to designated positions allows communication displaying different color light sources is positioned between a power source and a flashlight lens whereby a releasably-urging spring and rotatable, keyed cam ring serve to compress and release said spring to allow for color change.

Abstract: The present invention relates to a flashlight capable of generating and projecting multiple colors within one flashlight unit where said flashlight contains an extendable lens, a light source, a moveable member positionable at various locations to be moved across said light source, a rechargeable power source and a tail cap switch for ‘on’ and ‘off’ functions as well as dimming and brightening of a light source beam. The moveable member is slidably fixed to move perpendicular to a light source whereby movement to designated positions allows communication displaying different color light sources is positioned between a power source and a flashlight lens whereby a releasably-urging spring and rotatable, keyed cam ring serve to compress and release said spring to allow for color change.

Abstract: According to one exemplary embodiment, a system for processing transactions is provided that comprises a transaction processing circuit configured to receive transaction data relating to one or more transactions for the purchase of software applications from a digital application store. The transaction processing circuit is further configured to apply one or more business rules to the transaction data and to generate one or more transaction summary files. The transaction summary files are transmitted to a payment system configured to perform, based on the transaction summary files, at least one of recording revenue related to the transactions and causing payment to be distributed to developers of the software applications. At least a portion of the transaction processing circuit is implemented using a shared, scalable computing system.

Abstract: Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for receiving, from a client device, a first notification of an ad space from a seller, identifying ad conditions corresponding to an ad space inventory to which the ad space belongs comprising a first condition that identifies an allowed creative media type for the ad space inventory, sending a second notification requesting a bid on the ad space to bidders, each bidder representing a respective buyer, receiving bids from the bidders, each bid corresponding to a respective bid price, buyer, and a creative, determining that a first bid of the bids corresponds to a first creative having a media type different from the allowed creative media type, and identifying a preexisting arrangement between the buyer corresponding to the first bid and the seller and, based thereon, allowing the first creative to be served to the ad space.

Abstract: Eyeglass frame elements may include a bridge and temples, and for an accessory attached to eyeglasses, one or more clips. Each of these elements includes an attachment point to the lens. For this attachment point a terminal portion of a metal wire is received through a first of two apertures formed through a lens adjacent an edge thereof. A remaining portion of the metal wire is received through a second of the two apertures. A first bend in the metal wire between the terminal portion and the remaining portion located is formed between the two apertures. This first bend is adjacent to a surface of the lens. A second bend in the metal wire is formed adjacent the second of the two apertures so that at least part of the terminal portion is adjacent an outside edge of the lens.

Abstract: Eyeglass frame elements may include a bridge and temples, and for an accessory attached to eyeglasses, one or more clips. Each of these elements includes an attachment point to the lens. For this attachment point a terminal portion of a metal wire is received through a first of two apertures formed through a lens adjacent an edge thereof. A remaining portion of the metal wire is received through a second of the two apertures. A first bend in the metal wire between the terminal portion and the remaining portion located is formed between the two apertures. This first bend is adjacent to a surface of the lens. A second bend in the metal wire is formed adjacent the second of the two apertures so that at least part of the terminal portion is adjacent an outside edge of the lens.