Additional Application Containers allow you to scale your Service Plan with increased user traffic by providing additional runtime environments for Verj.io Applications.
They 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 Primary and Additional 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. All Additional Application Containers automatically load these updates, making them available to new end users.
Composition
By default, Service Plans do not have any Additional Application Containers, the Primary Application Container responds to end user requests.
Scalable Service Plans can be configured with multiple Additional Application Containers load-balanced with each other and the Primary Application Container.
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
Additional Application Containers can be restarted or stopped in the Service Plan details page of the Cloud Portal.
Stopping the Primary and all Additional Application Containers in a Service Plan will make your application unavailable until at least one is started again.