Skip to main content

 

Sizing OutSystems Platform

 

OutSystems

Sizing OutSystems Platform

To account for the expected impacts of scaling your applications, you need to know upfront which hardware best supports this growth.

There are three major factors you need to consider when sizing and scaling OutSystems Platform:

  1. Application logic - It keeps changing throughout the application life cycle from Development to Production. It has a major impact on server load.

  2. Data size - Tends to grow in a predictable manner.

  3. Integrations - Test all integrations on QA or Pre-Production environments for their response time. This will give you an idea on how they will behave in Production and of the impact on the application response time.

The following hardware recommendations ensure that your infrastructure is properly sized.

The information in this article applies only to on-premises or private cloud infrastructures.

Production environment

The following recommendations are applicable to any of the server roles you have in your OutSystems infrastructure.

# Requests per second 20 40 40+
Recommended setup - Dual Core processor
- 8GB RAM
- 80 GB HD (after OS install)
- Quad Core processor
- 12GB RAM
- 200 GB HD (after OS install)
Grow horizontally with multiple server building blocks with the same specs.

Non-Production environment

If you have many developers (16+) or you detect slowness in your non-production environment, you might want to use a dedicated Deployment Controller server to segregate the code compilation process.

# Active developers 5+ 8+ 16+
Recommended setup Front-end + Deployment Controller:
- Dual Core processor
- 8GB RAM
- 100 GB HD (after OS install)
Front-end + Deployment Controller:
- Quad Core processor
- 12GB RAM
- 200 GB HD (after OS install)
Front-end:
(Where the developers connect to)
- Quad Core processor
- 12GB RAM
- 300 GB HD (after OS install)

Deployment Controller:
(Where code compilation occurs)
- Quad Core processor
- 16GB RAM
- 500 GB HD (after OS install)
Additional developer - 0.25 core
- 512MB RAM
- Up to 8 Developers
- 0.25 core
- 0.5GB RAM
- Up to 16 Developers
Front-end:
(Where the developers connect to)
- 0.25 core
- 0.5GB RAM

Deployment Controller:
(Where code compilation occurs)
- 0.25 core
- 0.5GB RAM

Single server versus farm architecture

For critical Production and Development sites, OutSystems recommends a farm architecture.

Single-server architectures depend on the available technology upgrades at the time. Additionally, a single server that is super powerful may cost ten times as much as two servers with half the capabilities.

On the other hand, a farm architecture guarantees reliability and uptime in failure or maintenance events. That's not possible with a single server.

More Information

To learn more about how to set up your OutSystems infrastructure, check the Designing OutSystems infrastructures guide.