The Content Software for File system offers a converged deployment configuration as an alternative to the standard setup. In this configuration, hundreds of application servers running user applications are equipped with Content Software for File clients, allowing them to access the Content Software for File cluster.
Unlike the standard deployment that dedicates specific servers to Content Software for File backends, the converged setup involves installing a Content Software for File client on each application server. Additionally, one or more SSDs and backend processes (WekaFS) are integrated into the existing application servers.
The Content Software for File backend processes function collectively as a single, distributed, and scalable filesystem, leveraging the local SSDs. This filesystem is accessible to the application servers, much like in the standard Content Software for File system deployment. The critical distinction is that, in this configuration, Content Software for File backends share the same physical infrastructure as the application servers.
The Content Software for File system in converged mode with compute and storage on the same infrastructure. This blend of storage and computing capabilities enhances overall performance and resource usage. However, unlike the standard deployment, where an application server failure does not impact other backends, the converged setup is affected if an application server is rebooted or experiences a failure. The N+2 (or N+4) scheme still protects the cluster and can tolerate two concurrent failures. As a result, converged Content Software for File deployments require more careful integration and detailed coordination between computational and storage management practices.
In all other respects, this configuration mirrors the standard Content Software for File system, offering the same functionality features for protection, redundancy, failed component replacement, failure domains, prioritized data rebuilds, and seamless distribution, scale, and performance. Some servers may house a Content Software for File backend process and a local SSD, while others may have Content Software for File clients only. This allows for a cluster of application servers with a mix of Content Software for File software and Content Software for File clients.