I've recently been been looking at some significantly increasing cloud hosting costs for a client.
There are a lot of reasons why this is happening... but in short, a lot of additional cloud costs come from these three causes:
1. Incorrect cloud architecture
This could be: not using “build & burn” practices, failing to automatically spin up (and especially spin down) components as needed, etc.
2. Processing more data than is needed
This could be: the creation of too many environments, badly sized test databases, etc.
3. Having unnecessarily stringent NFRs for non-production
In this could be: the high specification of development or test environments, running batch jobs too often and when not needed.
There are a lot of reasons why this is happening... but in short, a lot of additional cloud costs come from these three causes:
1. Incorrect cloud architecture
This could be: not using “build & burn” practices, failing to automatically spin up (and especially spin down) components as needed, etc.
2. Processing more data than is needed
This could be: the creation of too many environments, badly sized test databases, etc.
3. Having unnecessarily stringent NFRs for non-production
In this could be: the high specification of development or test environments, running batch jobs too often and when not needed.
No comments:
Post a Comment