To add to the issue, the setup in this scenario was across separate AWS accounts – development, testing and production. In cases such as this where dozens of VMs are in play at once, keeping track can get out of hand. In order to do this, each developer needs their own VM which can replicate a production environment for the site – so depending on the development in each environment, some of these VMs can use massive volumes of compute resources. One Godel client, a major online fashion retailer, used a large content management system (CMS) which allows its front-end development team to build pages for their eCommerce site. When considering larger development teams, it is very possible – common, even – for this issue to add up quickly and quietly. As previously highlighted, this can incur creeping costs over time.

When developers have powerful access to spinning up new resources in development cloud environments, it is easy to find many resources being set up and promptly forgotten about. None of this required application code changes. Godel’s DevOps engineers have recently driven savings of up to 50% for clients’ cloud-based systems following three approaches.

The bottom line is that reducing spend whilst maintaining optimal performance is a high priority goal for many development teams and businesses. Migrating to the cloud reduces on-premise expenses across hardware and maintenance, but these savings can be eaten up when computing resource consumption accelerates. Drawing an overall cost-comparison between cloud computing and on-premise datacentres requires looking at many factors to find a black-and-white conclusion.

Waves complete cost