|By Toddy Mladenov||
|June 18, 2014 10:27 AM EDT||
At the Prepare for Multi-Cloud Future panel yesterday the guys from Equinix, Redapt, RightScale and Datapipe offered great insights about the challenges of using multiple clouds. One of those is of course estimating the cost of running your application in the cloud or in multiple clouds. With that in mind I wanted to elaborate a bit more on what should you think about when doing the estimate.
Quite often you will see IT or business teams estimate the cloud costs only based on the compute power and storage that they need. One quite often overlooked component of the cloud cost is the traffic (inbound and outbound) that can become significant charge depending on your application and its architecture.
Here is the list of things you will need to consider when estimating the cloud costs for your application:
- Compute workloads
Those can be workloads for your front-end servers, batch processing systems, middle tier and in some cases back-end databases.
Storage can be of two types: file or also called blob storage and database, which respectively can be relational, NoSQL or just table format (key/value pairs)
- Data Transfer
Data transfer can be inbound and outbound. Most of the cloud providers do not charge you for inbound traffic (this is traffic coming into their data center) but they charge you for outbound traffic (traffic coming out of their data center). Very common mistake when estimating the costs is not accounting for traffic between data centers - depending on the cloud provider you may or may not incur charges for such traffic.
- Support Plans
So far we have seen very few teams that account for the support costs when they estimate their move to the cloud. If you are big enterprise this may be included in your Enterprise Agreement but you need to make sure this is the case.
- Other Cloud Costs
This is the catch all bucket that may include but is not limited to additional services like diagnostics and monitoring, directory, analytics, API management etc. Most of the times those may be fixed subscription price but sometimes you should expect to have charge per transaction.
In majority of the cases you will not be able to properly estimate the costs the first time you do it. It is good to keep a check list as well as your historical costs because this can help you estimate the growth or use for other applications. RightScale's Plan For Cloud tool can be very helpful to get you started.
- Why Shutting Down TechNet Is Not a Problem for IT Pros
- Open Source in the Cloud - How Much Should You Care?
- Is Your Cloud Ready for the Enterprise?
- Business Strategy for Enterprise Cloud Startups
- The Importance of Private Clouds
- Cloud Computing Service Models
- Are There Other "as-a-Service" Cloud Offerings?
- Essential Cloud Computing Characteristics
- How Do You Choose Your Cloud Provider?
- There Is More to PaaS Than You Think