Private vs Public Cloud: Pricing

collection currency

Yesterday, we discussed using a Private vs Public Cloud for our Product Data Management needs. We’ll dive deeper into the differences between the two approaches over the next few days and give you an idea why we trust the private route. First up – pricing.

When developing a Cloud-hosted solution for SOLIDWORKS PDM, our partner EpiGrid considered utilizing a Public Cloud provider.  They discovered that AWS, Azure, and other Public Cloud providers base their billing on network traffic and usage of the server. This could mean wild shifts in pricing if there is a lot of check-out/check-in activity or data transfer.  These shifts would make it nearly impossible to predict what the platform’s cost would be month-to-month.

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.  Inconsistent pricing vs. consistency each month? Going with a Private Cloud was the obvious choice.

Another bonus – our Private Cloud infrastructure allows us to support our users quickly and seamlessly. DesingPoint’s support team has access to the back-end components of your Cloud-hosted server, so if anything goes wrong, we will have an Application Engineer 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.

Original content by Tanner Knight.