AWS Announces Amazon Aurora Supports PostgreSQL 12
infoq.comI'm just here to say that I took an exam for AWS Solutions Architect last week and I thought Aurora PostgreSQL was a made up service.
I feel like a fool.
I’ve looked pretty hard at moving my fairly large Postgres RDS to Aurora and the pricing is just very scary. I have a single 100GB instance running on fairly minimal hardware and serving a Django site with 6k monthly visitors. My usage is pretty concentrated during 9-6pm EST as I mainly serve US law firms and investment funds. Any idea if that will end up costing me a fortune to go Aurora? I’m worried about all of those requests in a short amount of time leading to it spinning up a lot of instances.
Aurora's autoscaler is fully in your control. Aurora Serverless is usage-based, but regular Aurora is just an AWS-optimized Postgres distro. You should not receive any surprise billing based on scaling, unless you specifically configure it to do so. Based on those usage patterns you explained you could do a scheduled scaling event that would scale up your Aurora cluster to have more capacity during business hours. If its a read-heavy workload then read replicas are a cheap and easy way to scale.
‘AWS optimized Postgres distro’ is perhaps underselling it a bit, while being broadly correct. The magic is in the storage engine which powers instantaneous failover, point in time restores and the newly released ‘serverless 2’ product (which would be ideal for the parent has)
You're spot on that Aurora is super-powerful for performance and scaling, giving it characteristics and controls that don't really exist elsewhere. I heard a great talk with their engineering lead about how they optimized Postgres internals to play nicely with S3.
I still think a small Aurora Postgres with some workday scaling events on a schedule would have more affordable and predictable if the bulk of the workload is 9-6 weekdays. Serverless Aurora is (finally) great, but expensive and really requires some extra work to optimize usages to minimize cost.
AWS is really expensive as you scale unfortunately.
Not really. It very much depends.
I don't think AWS RDS scales like that with "a lot of instances". The only time you would have so many instances is from how many read replicas you setup, and if you have a standby instance. RDS isn't like an EC2 ASG. I might be wrong though ='(
Source: An AWS Certs Scrub
At your current scale, just adding a slave for redundancy and hot take over should be enough?
There's also the aurora serverless way which may be interesting since your workload is only a few hours a day. Scale up automatically during the peak and wind down the rest of the time.
> Any idea if that will end up costing me a fortune to go Aurora?
Define a fortune.
Considering you can run a site like his off of a $10 VPS with room to spare for x10 more users, any dollar beyond that better be worth it.
Sure, going to $50 won't matter to most wallets, but at around $100 you're just getting ripped off and someone is having a laugh at your expense.
So I'd put 'paying a fortune' at around $100/month for his case.
> Sure, going to $50 won't matter to most wallets, but at around $100 you're just getting ripped off and someone is having a laugh at your expense.
This comes up on every AWS-related comment section.
$100/month for something I could do with VPS is an amazing bargain if it saves me even 2 hours of dev time every month.
As someone who used to maintain servers and databases first on dedicated hardware, then on colo servers, and later on vanilla EC2, I am so thankful for RDS. It's absolutely amazing not to have to worry about:
- failover
- scaling
- logs
- read(/write) replicas
- (restoring) backups
- monitoring
- maintenance windows
- minor version updates
- OS updates
...and that's probably not even a complete list.
Every VPS-like database management experience I've ever had has caused me a lot of lost sleep. It's just not worth it. I can't imagine why anyone would DIY this stuff if they're working with any kind of budget at all.
At the moment, I have an insurance company with hundreds of thousands of customers running on ~$1,000/mo. of AWS services. The modern cloud is amazing and a constant source of joy for someone like me, who has been doing web software for more than 20 years.
Most VPS providers tick most of the boxes on your list, so I'm not sure what you're on about.
Also $100 for his case would be $1 per 60 monthly visitors. I hope they're not planning to be ad-supported, because then they will be leaking money at an amazing rate.
Plus what is the point of scaling when you're losing money at any scale?
I run a site with roughly 2 million monthly visitors. On AWS it would cost me $20,000/month on traffic alone.
Instead I run it on 4 dedicated servers and a bunch of VPS, costing me around $500/month all-in-all.
I could hire a four system administrators for the money I save, to look after each of my four dedicated servers full-time. How does AWS beat that?
> Most VPS providers tick most of the boxes on your list, so I'm not sure what you're on about.
Which VPS provider are you talking about specifically?
> Plus what is the point of scaling when you're losing money at any scale?
My point is that I'm not losing money. I'm saving money by transferring unpredictable salary costs into predictable server costs.
> I run a site with roughly 2 million monthly visitors. On AWS it would cost me $20,000/month on traffic alone.
If this is a static site, 2 million monthly visitors on AWS would cost less than $5.
If it's a non-static site and none of those 2 million visits are cached, I still can't begin to imagine what your app is doing that it could possibly cost you $20,000/month. That would buy you a huge fleet of servers (something like 200 mid-to-large EC2 instances).
It doesn't sound like you have a sense of what AWS costs, even within an order of magnitude.
> Instead I run it on 4 dedicated servers and a bunch of VPS, costing me around $500/month all-in-all.
Four medium EC2 instances also cost ~$500/month all-in, so you're seemingly saving nothing. The layers of software on top of the (virtual) hardware are free.
> Which VPS provider are you talking about specifically?
Take any major one like OVH.
> If this is a static site, 2 million monthly visitors on AWS would cost less than $5.
If this was a static site I could run it for free. But it's not.
> Four medium EC2 instances.
That's not even a close to the specs of the dedicated servers I am using, nor is the site "just" those four servers. Those $500 include everything from domains to backups, to various back- and front-end VPS.
>I still can't begin to imagine what your app is doing that it could possibly cost you $20,000/month.
I just told you. The egress traffic alone would cost me that much.
Look up what 500TB-1000TB of egress traffic would cost me on AWS. Last I checked it was easily north of $20,000 even with their volume discounts.
Meanwhile I can buy dedicated servers with 1Gbps dedicated and unmetered bandwidth for 60-70 bucks/month nowadays, and I won't have to worry about paying a dollar more - and certainly not thousands of dollars.
And no it's not the kind of traffic you can just run through a CDN. I would if it'd make sense. In fact I already use Cloudflare for those areas where it makes sense - shaves off around 100TB.
You’d likely get discounts with that volume of spend and you can always use a cheaper third party CDN.
Based on your totals your numbers are suspect. You’re saying each visitor would cost you 100$ in bandwidth fees? At the lowest bandwidth pricing level that’s over a terabyte per user, per month, if you go through cloudfront.
You really should check your maths.
What’s the reason for using Aurora?
Where's MySQL 8 for Aurora? :-/