The Application Container is the component of a Service Plan that provides the runtime environment for Verj.io Applications, or to put it another way, it is the component that end users directly interact with.
Application Containers are functionally equivalent to a Verj.io On-Premises environment with the same Verj.io Version.
Applications
Requests from end users are internally routed through to the Service Plan's Application Containers, which respond as defined by the application.
New applications, and changes to existing applications, can be deployed to a Service Plan’s Application Filesystem via the Studio. Application Containers automatically load these updates, making them available to new end users.
Composition
Every Service Plan comes with one Application Container. Scalable Service Plans can be configured to have multiple identical Application Containers.
The configuration of the Service Plan determines various attributes of its Application Containers, including the amount of memory available to them, which in turn affects the total number of concurrent end users that can be supported.
Troubleshooting
The Studio’s Visual Debugger can remotely connect to an Application Container and help troubleshoot your application.
Your application’s logs, can be viewed in the logging section of the Cloud Portal. Reports on the Application Containers' performance and resources can be generated in the Cloud Portal’s statistics page.
Controlling Application Containers
An Application Container can be restarted or stopped in the Service Plan details page of the Cloud Portal. Stopping all Application Containers in a Service Plan will make your application unavailable until at least one Application Container is started again.