As you can see, however, the upfront payment is over $30,000! If you choose instead to pay 100% of the yearly cost up front, you’d end up saving $681.78 over the course of the year versus Google Cloud Platform, or 2.3%. If you opt to pay over $18k up front using the “partial upfront” model, you arrive at a lower price, saving $44 dollars (not thousands) over the course of the yearĪmazon Web Services, all upfront, 1 year estimate: Over a one-year term with Amazon, if you commit to pay for the instance for that entire period, and you opt for the “no-upfront” option, you still end up with a 13% higher cost than making no commitment to Google.Īmazon Web Services, partial upfront, 1 year estimate:
Here are the costs for our example app with Amazon’s Reserved Instance pricing:Īmazon Web Services, no-upfront, 1 year estimate: Over the course of a year, going with Google would save you just over $19,000!Īmazon Web Services has an alternate payment model, where you can make a commitment to run infrastructure for a longer period of time (either 1 or 3 years), and opt to pay some portion of the costs up front, which they call Reserved Instances. Even without that, pricing before the discount comes in at $3729.86, or an 11% discount off Amazon’s on-demand rates.
#GOOGLE CLOUD MONEY MAKING FULL#
Since we didn’t autoscale or otherwise vary our system over the course of the month, the full 30% discount applies. Why? Google includes an automatic discount called Sustained Usage Discount, which reduces the cost of long-running instances. It’s important to note that right away things don’t look equivalent, with Google’s pricing being 38% lower. Here is the output of the pricing calculators: Any discrepancies are likely due to pricing or calculator changes following the publishing of this post. Please note that we completed these calculations on January 12, 2015, and have included the output prices in this post. We can use calculators that each provider offers to find out correct pricing quickly: To explain the nuances of cloud pricing, let’s use Google Cloud Platform and Amazon Web Services as the example cloud infrastructure providers, and start at the most simple, on-demand model. In Figure 1, you can see our example application logical architecture looks like this: Let’s assume for now that the workload is entirely static, and autoscaling isn’t being used (oh don’t worry, we’ll add that and more back in later). The Cassandra cluster will need five instances with a higher memory footprint.The application layer will need four instances for image processing and storage control.The marketing front end shouldn’t need more than two instances for redundancy.Therefore we should only need four regular instances for this layer. We expect about 350 requests per second given this number of users. The API frontend instances can respond to roughly 80 requests per second.And on the back end, a Cassandra cluster to store operational metadata.įor capacity planning, we have scoped as follows:.An application layer that will process and store images as they come in or are accessed.This portion will consume the majority of the compute cycles. An API frontend that mobile devices will contact for requests and actions.Our example application has 4 components: Let’s go through what instance types this application will need to meet that user-driven workload and then price out what that will cost in an average month on Google Cloud Platform and compare against Amazon Web Services. This application shares pictures in some way, and has about 5 million active monthly users. For this example, let's look at a fairly common scenario, a mobile application with its backend in the cloud. To help you work this through, we’ve created an example for you. How do you figure out what each costs and make a choice? Some bill in different time increments, and many offer a variety of payment structures, each with differing economic ramifications.
In addition, no two clouds are the same! Some bundle components while others offer more granular purchasing. Cloud infrastructure systems create a whole new range of variables in these complex equations. Costs come from a variety of sources, and every approach to delivering infrastructure has its own tradeoffs and complexities. When designing infrastructure systems, whether creating new applications or deploying existing software, it’s crucial to manage cost.
0 kommentar(er)
