supports both hyper-converged and compute and storage separated architectures.
While running compute and storage layers apart from each other, it is possible to scale compute and
storage resources independently, with different leverages regardless from each other. As a result, the
system better fits the task while CapEx and OpEx go through the floor, since there is no
need to purchase hardware that will be essentially wasted. Thus the system can be created specifically
for a particular task.
When running StarWind in compute and storage separated scenarios where clusters are running out of compute power, all that is needed is to add to the hypervisor node more CPU and RAM, while the storage capacity and performance will remain the same. Likewise, if the system will be running out of storage IOPS
or TBs, that dimension can be upgraded easily without affecting the compute power by adding storage node now.