The best practice to enter your end application is by using a web application firewall (WAF), though a reverse proxy or a firewall is also possible.
Scaling is possible in several ways:
Vertically, by adding more CPU/RAM/etc. to the server, web application, etc.
Horizontally, by expanding the infrastructure (cloud) or hardware (on premise) by adding more servers, web applications, etc. Adding web applications (and Indiciums) in the cloud automatically leads to expanding the infrastructure. On premise, adding hardware or virtual machines is required before adding more web applications (and Indiciums). A load test will give an estimation of the required number of Indiciums.
For horizontal scaling, load balancing is required. Load balancing is the process of distributing a set of tasks over a set of resources, to make their overall processing more efficient. The best practice is using WAF.
Sticky sessions, a.k.a. session persistence, is a process in which a load balancer creates an affinity between a client and a specific network server for the duration of a session, (i.e. the time a specific IP spends on a website). For your end application, built by the Thinkwise Platform, sticky sessions are essential in a load-balanced environment.
To reduce the risk of a single point of failure, a second portal can be added.
The same applies to the SQL server: to reduce the risk of a single point of failure, you can add a second one.
Supported setups are:
- SQL Always On.
- SQL Clustering (active/passive or active/active).