Effectively using AWS Reserved Instances
stripe.com
Effectively using AWS Reserved Instances
1–10 of 123 posts
Re: Effectively using AWS Reserved Instances
#2> To automate this, we built an ETL process in SQL and Python that detects when we fall outside this band and automatically prepares a purchase for us to approve.
@Stripe: Will this (or parts of it) be open sourced?
Re: Effectively using AWS Reserved Instances
#3Similar idea to rolling your own, my company uses Cloudability for AWS purchase planning. It saved a bunch of money as far as I remember.
Re: Effectively using AWS Reserved Instances
#4Google Cloud's pricing approach seems much more sane than each company having to spend all this effort juggling reserved instances.
Re: Effectively using AWS Reserved Instances
#5Despite being a strong advocate for AWS, this is where I will say Google completely outshines Amazon.
Google's approach to pricing is, "do it as efficiently and quickly as possible, and we'll make sure that's the cheapest option".
AWS's approach is more, "help us do capacity planning and we'll let you get a price break for it.".
Google applies bulk discounts after the fact, AWS makes you ask for them ahead of time.
Re: Effectively using AWS Reserved Instances
#6The best answer is of course not to at all. Burst into the cloud, static workloads in your own DC.
Re: Effectively using AWS Reserved Instances
#7I thought that payment processors are using their own hardware. How is AWS protecting their own customers' privacy? - can uncle Bob insert his fancy flash drive, copy my data, and sell it? Before you say it is encrypted - where does the encryption happen and doesn't AWS employees have access to the keys too?
Re: Effectively using AWS Reserved Instances
#8Despite being a strong advocate for AWS, this is where I will say Google completely outshines Amazon. Google's approach to pricing is, "do it as efficiently and quickly as possible, and we'll make sure that's the cheapest option". AWS's approach is more, "help us do capacity planning and we'll let you get a price break for it.". Google applies bulk discounts after the fact, AWS makes you ask for them ahead of time.
Using GCC still feels like comparing an early android to a modern iOS. I guess they have to sell it cheap when the features and quality is not there.
Re: Effectively using AWS Reserved Instances
#9Despite being a strong advocate for AWS, this is where I will say Google completely outshines Amazon. Google's approach to pricing is, "do it as efficiently and quickly as possible, and we'll make sure that's the cheapest option". AWS's approach is more, "help us do capacity planning and we'll let you get a price break for it.". Google applies bulk discounts after the fact, AWS makes you ask for them ahead of time.
[deleted]
Re: Effectively using AWS Reserved Instances
#10The best answer is of course not to at all. Burst into the cloud, static workloads in your own DC.
How exactly does that solve the problem? Don't you have to do the same capacity planning to decide how many servers to buy for your datacenter? Except you get less flexibility because you can't buy servers and have them instantly available like you can for reserved instances?
Also, what kind of workloads are you running that don't require databases? The biggest expense in any distributed system is moving data. If you have a datacenter with all the data, you've to move that data to the cloud and back for every bursted request. Whatever you might save in running your own DC will be lost to bandwidth charges.
And on the topic of running your own datacenter, it's unlikely you can run it as efficiently as AWS. What you might save in not paying AWS's profit margin you will probably spend in not being able to be as efficient as they are.