Last week we gave you an overview of the topic of Private vs Public Cloud. Starting with this post, we will now dive deeper into the differences between the two approaches over the next few weeks and give you an idea why we chose to go the private route.
When developing a Cloud-hosted solution for SOLIDWORKS PDM, our partner EpiGrid considered utilizing a Public Cloud provider, and with each provider, the pricing of the platform made it nearly impossible to predict what the cost would be month-to-month. With AWS, Azure, and the likes, you are billed on network traffic and usage of the server. This could mean wild shifts in pricing month over month if there is a lot of check-out/check-in activity or data transfer.
EpiGrid insisted on a stable pricing structure, where you know what your bill will be month-to-month regardless of traffic or usage. This was only possible with a Private Cloud.
Also, thanks to our Private Cloud infrastructure, we're able to support our solutions quickly and seamlessly from the user's perspective. Our support team has access to the back-end components of your Cloud-hosted server, so if anything goes wrong, we will have a support agent logging into the server within minutes to troubleshoot. And in the case of the inevitable hardware failure, our hosting provider has boots on the ground in the data centers to quickly and discreetly swap out any faulty hardware.