Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Amazon RDS for PostgreSQL

aws.amazon.com

Post reply on HN
Print view View original

101–110 of 246 posts

Re: Amazon RDS for PostgreSQL

#101

Post by craigkerstiens »

giovannibajo1 wrote: post #99
craigkerstiens wrote: post #83

Earlier quoted context omitted.

disclaimer: Heroku PM here By default our followers and HA is automatically cross AZ. You also have an ability to create followers across region, but we do not automatically failover on those due to latency.

Can you please explain the value proposition of using Heroku Postgres vs RDS now? Heroku's solution is 2 to 4 times more expensive for the same type of DB, and RDS even allows for reserved instances to further lower the bill.

There are a variety of differences overall.

One area is we're focused more on delivering more guidance and expertise around what you're doing with your database, in addition to ensuring your database is healthy and running. An example of this is notifications that we deliver around unused indexes, where you may benefit from other indexes, or other places where you can quickly optimize your DB. This starts to free up a DBA to add higher value tasks or for smaller shops lets you get by longer without a need for a DBA.

Another big area is features we deliver on top of Postgres. This ranges from followers which all you to easily scale read traffic, or allow for your database to be replicated across not just AZs but also regions. There's the other spectrum of this as well including dataclips. Dataclips make it easy to share data in a simple way, as well as build richer dashboards by integrating with google docs, or quickly prototyping APIs.

If you're curious on various technical details we'll be documenting that soon but would be happy to correspond via email, craig at heroku.com

Re: Amazon RDS for PostgreSQL

#102

Post by adrianh »

sync wrote: post #79
adrianh wrote: post #4

This is HUGE! I'm using the AWS stack for http://www.soundslice.com/ and I've been using MySQL instead of Postgres, purely because my hatred for MySQL is less than my hatred for being a sysadmin. It was a tradeoff, and I miss Postgres dearly every time I use MySQL. This new Amazon offering solves that. I wrote a little more about my AWS setup here: http://www.holovaty.com/writing/aws-notes/

Hey, just took a look at soundslice, looks super nice. FYI, it doesn't look your payment modal works on smaller browser windows: https://www.monosnap.com/image/UvJbxMQEwkzqLH5btNJ7a9G6Q ... no visible pay button, and the modal itself scrolls when you scroll the page.

Thanks very much -- I've just done a band-aid solution and moved the payment modal up, but we'll get a better solution up soon. Much appreciated!

Re: Amazon RDS for PostgreSQL

#103

Post by elob36 »

gdulli wrote: post #30
yumraj wrote: post #8

I've heard about PostgreSQL and know that HN community raves about it, but am currently using RDS with MySQL. Does it make sense to migrate to PostgreSQL, I don't have a lot of data as I'm in the early stage? What are the primary advantages that PostgreSQL provides over MySQL? Any advise/pointers is appreciated.

edited to add: - timestamp with time zone - More robust, fewer crashes, less corruption of data - More features (JSON data type, partial indexes, function/expression indexes, window functions, CTEs, hstore, ranges/sequences/sets, too many to list) - More disciplined (doesn't do things like auto-truncate input to get it to fit into a column) - Not owned by Oracle, it's actively developed, regular major release schedul…

To me, the MySQL query optimizer (single index in a query) was the proverbial straw that broke the camel's back.

My group is developing all new applications in PostgreSQL and we would like to migrate our legacy apps away from MySQL.

Re: Amazon RDS for PostgreSQL

#104

Post by elob36 »

rektide wrote: post #64
yumraj wrote: post #8

I've heard about PostgreSQL and know that HN community raves about it, but am currently using RDS with MySQL. Does it make sense to migrate to PostgreSQL, I don't have a lot of data as I'm in the early stage? What are the primary advantages that PostgreSQL provides over MySQL? Any advise/pointers is appreciated.

If you didn't care yesterday, I HIGHLY ENCOURAGE AND RECOMMEND YOU NOT CARE TODAY.

He cares today because he now has an option.

Re: Amazon RDS for PostgreSQL

#105

Post by fat0wl »

adrianh wrote: post #4

This is HUGE! I'm using the AWS stack for http://www.soundslice.com/ and I've been using MySQL instead of Postgres, purely because my hatred for MySQL is less than my hatred for being a sysadmin. It was a tradeoff, and I miss Postgres dearly every time I use MySQL. This new Amazon offering solves that. I wrote a little more about my AWS setup here: http://www.holovaty.com/writing/aws-notes/

Yea I was using MySQL on RDS just to escape the Heroku monolith. Funny that Heroku announced a new Postgres pricing model that is VERY expensive compared to old setup (https://news.ycombinator.com/item?id=6712570) just in time to be wiped off the map by RDS.

Re: Amazon RDS for PostgreSQL

#106

Post by justincormack »

vec wrote: post #84
pbreit wrote: post #54

Earlier quoted context omitted.

Hmmm...I was wondering why MySQL is still much more widely used.

Inertia, largely. Postgres is more scalable and has quite a few nonstandard additions that are insanely useful from time to time, but it's not always a drop-in MySQL replacement. If you're just writing something simple like a blog or CMS then you don't need the extra functionality. Plus Wordpress has a hard requirement for MySQL, and like it or not a huge number of projects still use it as a framework.

but if its just a blog use mongo not mysql. non relational is a benefit and you have backups... postgres for real stuff.

Re: Amazon RDS for PostgreSQL

#107

Post by cbsmith »

falcolas wrote: post #94
cbsmith wrote: post #70

Earlier quoted context omitted.

As someone who is familiar with the rigamarole of PCI compliance, I respectfully disagree.

Disagree with what? Keeping your own backups? Probably not - if you're not keeping offsite backups, you're begging to go out of business. With needing a DBA, even if you're still on RDS? I don't see what that has to do with PCI compliance. With RDS only removing the up-front setup pain, at the cost of ongoing maintenance... as someone who is also familiar with PCI (and HIPPA, and DOD) compliance, I respectfully disag…

> Disagree with what?

I disagree with the notion that RDS removes remarkably little of the pain of running a database instance.

Yes, there are projects where RDS is not a great solution, but it definitely simplifies a lot of stuff. The notion that it "only removes up-front setup pain" is silly. If you manage your databases correctly, up-front setup pain should be the vast majority of all your basic admin operations. The "at the cost of ongoing maintenance" part is a real head scratcher for me. RDS basically gives you everything you'd have with a DB on an AWS instance except a local login, which one tries to avoid using like the plague anyway.

Re: Amazon RDS for PostgreSQL

#108

Post by LVB »

I've only ever used S3, but some of these AWS offerings do look interesting for my little projects. My question is, how do hours get calculated for billing? If I had my super low traffic blog using RDS, would I incur a few microseconds of time per DB hit, or is it rounded up to an hour, or is it the total time the DB is available period?

Re: Amazon RDS for PostgreSQL

#109

Post by dangrossman »

LVB wrote: post #108

I've only ever used S3, but some of these AWS offerings do look interesting for my little projects. My question is, how do hours get calculated for billing? If I had my super low traffic blog using RDS, would I incur a few microseconds of time per DB hit, or is it rounded up to an hour, or is it the total time the DB is available period?

You would be paying for 24 hours each day. You are renting a managed virtual server, and you pay for each hour this server is running in addition to usage fees for storage and IO operations when it's actually being accessed. It'd be $20-30/month to host the database for a very small blog.

Re: Amazon RDS for PostgreSQL

#110

Post by dpritchett »

craigkerstiens wrote: post #101
giovannibajo1 wrote: post #99

Earlier quoted context omitted.

Can you please explain the value proposition of using Heroku Postgres vs RDS now? Heroku's solution is 2 to 4 times more expensive for the same type of DB, and RDS even allows for reserved instances to further lower the bill.

There are a variety of differences overall. One area is we're focused more on delivering more guidance and expertise around what you're doing with your database, in addition to ensuring your database is healthy and running. An example of this is notifications that we deliver around unused indexes, where you may benefit from other indexes, or other places where you can quickly optimize your DB. This starts to free up…

Heroku customer here, can verify that dataclips are awesome. Haven't done the math on price vs. performance lately though.
Post reply on HN