|I have my own feelings on the Cloud computing movement, but I have to earnestly research it as a fiscally pleasing alternative to a hardware purchase needed for a large database solution I am developing. Amazon's AWS is the suggested service.
After researching the pricing of the service, it appears that it may quickly become costly for a server that must remain up 24/7/365 and is constantly updated in batches of 10-100k rows per second. The kicker is that this database server is for internal use only so if we hosted it in our network, it would not increase our in/outbound bandwidth, however if hosted in the cloud, it would, and we would also get charged for this from AWS's side.
According to their site, storage costs are:
Amazon EBS Volumes
• $0.10 per GB-month of provisioned storage
• $0.10 per 1 million I/O requests
While data transfers are:
Data Transfer In US EU Regions APAC Region
All Data Transfer $0.10 per GB $0.10 per GB
Data Transfer Out US EU Regions APAC Region
First 1 GB per Month $0.00 per GB $0.00 per GB
Up to 10 TB per Month $0.15 per GB $0.19 per GB
Next 40 TB per Month $0.11 per GB $0.15 per GB
Next 100 TB per Month $0.09 per GB $0.13 per GB
Over 150 TB per Month $0.08 per GB $0.12 per GB
Also, I won't be able to accurately estimate volume usage, IO's or data transfers until the system were to go into production. However, it can't go into production until I have chosen a hardware solution. The cloud's pricing system is making it more difficult because I could end up racking up huge bills once it goes prod.
My question is: Is it possible to make the decision to go with a cloud service for a new system? Or is it only viable for systems where X, Y and Z are known? And if this is the case, why not just stay with the current physical hardware?