The requirements for deploying WSO2 products can change based on the deployment scenario and pattern used. The recommendations in this topic are for general production use, assuming moderate load conditions. For situations where a high volume of traffic is expected and larger deployments, these guidelines may not be sufficient. See Troubleshooting in Production Environments for information on how to obtain and analyze information to solve production issues. The following are the topics addressed in this section.
...
Prior to installing any WSO2 Carbon-based product, it is necessary to have the appropriate hardware and software necessary for running the product.
| Note |
|---|
Note: The specifications listed in this section are general requirements for setting up a WSO2 product in a production environment. These specifications may vary for some WSO2 products, so check the installation prerequisites for the specific product when setting up your WSO2 product instance. |
Hardware requirements (per WSO2 product instance)
| Physical |
Disk space is based on the expected storage requirements that are calculated by considering the file uploads and the backup policies. For example, if three WSO2 product instances are running in a single machine, it requires a 4 GHz CPU, 8 GB RAM (2 GB for the operating system and 6 GB (2 GB for each WSO2 product instance)) and 30 GB of free space. |
| Virtual Machine |
Three WSO2 product instances running would require VM of 4 compute units, 8 GB RAM and 30 GB free space. |
| EC2 |
Three WSO2 product instances can be run in 1 EC2 Extra-Large instance. Based on the I/O performance of the c3.large instance, it is recommended to run multiple instances in a larger instance (c3.xlarge or c3.2xlarge). |
| Cassandra data nodes |
For more information, see the Cassandra documentation on hardware recommendations for enterprise implementations. |
...
| Info |
|---|
Note: When using SUSE Linux, it ignores |
...