Abstract: Systems for managing static assets of web applications. A method embodiment includes identifying a web application that comprises a code base and a set of static assets, then separating the code base of the web application from the set of static assets that are referenced by the web application. The code base is deployed as application services whereas the static assets are deployed as static asset containers. Specifically, the set of static assets referenced by the application services are deployed in containers that are instantiated separately from where the application services are instantiated. Requests to access the application services and requests to access the static assets are tracked by taking performance measurements of the systems that process the accesses. Dynamic scaling of static asset containers is done independently from dynamic scaling of the application services. The dynamic scaling is based on combinations of measured usage and/or any system performance characteristics.

Abstract: Systems for managing static assets of web applications. A method embodiment includes identifying a web application that comprises a code base and a set of static assets, then separating the code base of the web application from the set of static assets that are referenced by the web application. The code base is deployed as application services whereas the static assets are deployed as static asset containers. Specifically, the set of static assets referenced by the application services are deployed in containers that are instantiated separately from where the application services are instantiated. Requests to access the application services and requests to access the static assets are tracked by taking performance measurements of the systems that process the accesses. Dynamic scaling of static asset containers is done independently from dynamic scaling of the application services. The dynamic scaling is based on combinations of measured usage and/or any system performance characteristics.

Abstract: Systems for managing static assets of web applications. A method embodiment includes identifying a web application that comprises a code base and a set of static assets, then separating the code base of the web application from the set of static assets that are referenced by the web application. The code base is deployed as application services whereas the static assets are deployed as static asset containers. Specifically, the set of static assets referenced by the application services are deployed in containers that are instantiated separately from where the application services are instantiated. Requests to access the application services and requests to access the static assets are tracked by taking performance measurements of the systems that process the accesses. Dynamic scaling of static asset containers is done independently from dynamic scaling of the application services. The dynamic scaling is based on combinations of measured usage and/or any system performance characteristics.

Abstract: Systems for managing static assets of web applications. A method embodiment includes identifying a web application that comprises a code base and a set of static assets, then separating the code base of the web application from the set of static assets that are referenced by the web application. The code base is deployed as application services whereas the static assets are deployed as static asset containers. Specifically, the set of static assets referenced by the application services are deployed in containers that are instantiated separately from where the application services are instantiated. Requests to access the application services and requests to access the static assets are tracked by taking performance measurements of the systems that process the accesses. Dynamic scaling of static asset containers is done independently from dynamic scaling of the application services. The dynamic scaling is based on combinations of measured usage and/or any system performance characteristics.

Abstract: Embodiments of a Bundle Configuration Utility (BCU) for configuring network deliverable pluggable components for deployment in embedded servers are described. Preferences of a pluggable component may be accessed at runtime on the embedded server. The BCU may enable the configuration of the preferences prior to distribution. The BCU may provide functions including, but not limited to: providing a list of preferences; allowing preference values to be changed; updating the preferences in the pluggable component; creating a new pluggable component with a new set of preferences; and resetting the preferences in the pluggable component to default values. In one embodiment, pluggable components may be configured using a graphical user interface of the BCU. In one embodiment, the BCU may include a command line interface with commands for configuring pluggable components. In one embodiment, multiple pluggable components may be configured by the BCU in batch mode.

Abstract: Embodiments of a Bundle Configuration Utility (BCU) for configuring network deliverable pluggable components for deployment in embedded servers are described. Preferences of a pluggable component may be accessed at runtime on the embedded server. The BCU may enable the configuration of the preferences prior to distribution. The BCU may provide functions including, but not limited to: providing a list of preferences; allowing preference values to be changed; updating the preferences in the pluggable component; creating a new pluggable component with a new set of preferences; and resetting the preferences in the pluggable component to default values. In one embodiment, pluggable components may be configured using a graphical user interface of the BCU. In one embodiment, the BCU may include a command line interface with commands for configuring pluggable components. In one embodiment, multiple pluggable components may be configured by the BCU in batch mode.