Is Hyper.Net scalable?
The Hyper.Net transformation process is typically installed on a dedicated server (known as the “transformation server”) to keep resource-intensive tasks from slowing the functionality of your SharePoint servers. Installed in this way, Hyper.Net has no impact on the speed of SharePoint.
One Hyper.Net transformation server configured using the minimum requirements can typically manage unlimited numbers of documents and thousands of transformation requests per day. When installed on a server providing the recommended resources, Hyper.Net is capable of handling the needs of even very large document sets and high-volume transformation activity. Actual results are dependent on server capacity, document volume, document size and document content. The transformation process can also be configured to execute transformation requests in parallel.
Using the transformation server approach, Hyper.Net services are infinitely scalable through the organization or enterprise without impacting the SharePoint infrastructure and independent of how the SharePoint infrastructure grows. One or more SharePoint libraries can be configured to send transformation requests to any desired Hyper.Net transformation server.
Existing customers have implemented both centralized and decentralized transformation processes.