Amazon RDS now supports PostgreSQL 9.6.1(postgresql.org) |
Amazon RDS now supports PostgreSQL 9.6.1(postgresql.org) |
I suppose they have more experience with MySQL given that Youtube runs on it...
Obviously it's not their focus, but this is a fundamental selling point to cloud DB's.
See for example this staggering list of hosting providers in Europe: https://www.postgresql.org/support/professional_hosting/euro...
Yes, most of those are smaller companies. But some of these companies are directly involved in the development of PostgreSQL (just look at the PostgreSQL-hackers mailing list), so they should really know what they are doing!
I think you bring up a good point. I'm going to put aside my bias and give a smaller company a shot. Thanks for sharing.
When someone like Heroku offers a competing product, the fact that the product is also being run on EC2 is only a part of the overall story. Over time, AWS will probably be less and less happy with earning just the bare infrastructure dollars for such use.
I wanted to use PostgreSQL for a whole host of reasons, but not so much that we wanted to certify our own instances.
It's basically (a better) Heroku with an emphasis on enabling HIPAA/HITECH compliance. They do both app and DB hosting (including Postgres). And it's on AWS so integrates easily with existing infrastructure/code.
Disclaimer: Biased as I know the founders and we use the product. But they are good people and it's a good product!
That's something I heard that used to be true but not sure whether it's still required with upgrades to S3 over the years...
What is more exciting is you can leverage Redshift MPP architecture with this method.
I'm super excited about it. It's great to have more modern managed services on AWS especially since this brings Postgres out of the Stone Age. Lots of good JSON support added in 9.5 and 9.6.
Previously only 9.4 was available.
[0] https://aws.amazon.com/about-aws/whats-new/2016/04/rds-postg... [1] https://forums.aws.amazon.com/thread.jspa?threadID=240278
If needs once a week downtime for half an hour for patches. But if you use multi AZ deployment with 2 instances it does this without any actual downtime. Automatically manages the failover for you.
Provisioned IOPS are very expensive. For small loads use bigger general purposes SSD say 100 to 200gb and it works OK. The IOPS are burstable so it works out OK.
I agree on the IOPS - just get a larger disk (min 100G) even if you'll never use it. Storage is cheap. It's supposed to give you 3k IOPS but doesn't actually give you anywhere near that (but it is still fast). If you do need guaranteed IOPS, then it's wallet-opening time.
Half an hour downtime once a week? This sounds bad.
It seems to be that it's cheaper but it's hard to compare without knowing what the Heroku instances are.
That said, thanks for the link; I've voted for it and will keep an eye out there for future updates.
Compose is in a sweet spot right now. They run with the speed of a startup, but have access to IBM's massive resources. Really the best of both worlds.
Here are the exact words from Amazon:
> The Amazon RDS maintenance window is your opportunity to control when DB Instance modifications (such as scaling DB Instance class) and software patching occur, in the event they are requested or required. If a maintenance event is scheduled for a given week, it will be initiated and completed at some point during the maintenance window you identify. Maintenance windows are 30 minutes in duration. The only maintenance events that require Amazon RDS to take your DB Instance offline are scale compute operations (which generally take only a few minutes from start-to-finish) or required software patching. Required patching is automatically scheduled only for patches that are security and durability related. Such patching occurs infrequently (typically once every few months) and should seldom require more than a fraction of your maintenance window. If you do not specify a preferred weekly maintenance window when creating your DB Instance, a 30 minute default value is assigned. If you wish to modify when maintenance is performed on your behalf, you can do so by modifying your DB Instance in the AWS Management Console, the ModifyDBInstance API or the modify-db-instance command. Each of your DB Instances can have different preferred maintenance windows, if you so choose.
Running your DB Instance as a Multi-AZ deployment can further reduce the impact of a maintenance event. Please refer to the Amazon RDS User Guide for more information on maintenance operations.
Just build a HA RDS Cluster yourself with Click and Scale, than you can sell it to me with ~25% higher prices than the EC2 instances. Btw. AWS RDS is cheaper than most other competitors like ElephantSQL.
Also, as pointed out in the parent post, some of the hosting providers such as us (Aiven, https://aiven.io) are directly involved in PostgreSQL development and one of the bugfixes in the latest releases (9.6.1 and 9.5.5) that just came out was contributed by us.
With SQL server it was about ~50seconds.
2 minutes seems like a Long time but I'm curious now and want to test this again and maybe blog about it.
Apparently it was added in April: https://aws.amazon.com/about-aws/whats-new/2016/04/rds-postg...
That said, we are equipped to run the 'fast dedicated hardware' solution (we come from a managed services background) -- just write me, pjlegato at databaselabs.io, and I'll get you set up.
That page needs some love, thank you for the solid comment. I think the features we list cover your comments, but let me know if you have specific questions or other features you'd like to see!
Source: am Aptible CEO