News for hackers. Stuff that matters.
Re:Amazon RDS for PostgreSQL by adrianh on Thursday November 14, 2013 @12:23PM (#6733621)
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/

Re:Amazon RDS for PostgreSQL by fat0wl on Thursday November 14, 2013 @02:55PM (#6735056)
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 by fat0wl on Thursday November 14, 2013 @04:21PM (#6735671)
hey who downvoted this without replying?!

Last time I badmouthed Heroku on here I got a reply from one of their employees asking me to fill out support tickets for errors I was getting in their apps......

O_o they're watching.

Re:Amazon RDS for PostgreSQL by avenger123 on Thursday November 14, 2013 @04:51PM (#6735895)
No one's watching. Your initial comment just really didn't add any value. Calling Heroku monolith compared to Amazon is an understatement and I don't see Heroku being "wiped off the map" from this.
Re:Amazon RDS for PostgreSQL by ceejayoz on Thursday November 14, 2013 @05:23PM (#6736114)
https://twitter.com/scottvdp/status/401111184092315648

> RDS 4XL vs Heroku Mecha: 40% cheaper on demand, 74% cheaper 1 year reserved, 82% cheaper 3 year reserved... with more features and capacity.

If that's true, Heroku's Postgres offering isn't going to do well. "Wiped off the map" may be an overstatement, but not by that much.

Re:Amazon RDS for PostgreSQL by fat0wl on Thursday November 14, 2013 @05:50PM (#6736282)
If you listen closely you can hear the sound of an army of devteams uploading DB exports to Amazon....

& it would be louder if the rest could figure out where to put the custom DB URL parameter ;D

Re:Amazon RDS for PostgreSQL by fat0wl on Thursday November 14, 2013 @05:28PM (#6736139)
I wasn't calling Heroku a monolith because they're a huge company -- it's because they suck you in & then youre forever stuck in their web of services. I bet they start bleeding a lot of money now that there is an easy-to-use alternative for Postgres hosting on a well-known platform. Heroku epitomizes the idea of overcharge + vendor lock-in & people only put up with their high prices because they don't have the time to figure out a better configuration. Database is the easiest thing to jump ship with, you just have to change 1 URL.

It's a shame that Amazon has some proprietary idea of a machine image, but my ideal hosting scenario is just App Server Machine Image + DB + any Machine Images required for extra services. Shouldn't have to choose between several paid services that are just different APIs into an app server component you should have direct access to.

I don't understand how the open source community can be so into Heroku given that it's basically just wrapping open source software & charging for it, getting away with it by saying they're charging for the admin UI or whatever.

Re:Amazon RDS for PostgreSQL by rpedela on Thursday November 14, 2013 @06:44PM (#6736599)
Just like AWS, you pay Heroku to simplify your system administration. You don't have to like Heroku's product but there is a place for it. I do not use Heroku but it makes total sense if you have an app you need to deploy and you don't know system admin, don't want to do system admin yourself, or can't afford a system admin.

GitHub just "wraps up" git and charges for it and I am happy to pay them. Setting up a git server is a royal pain in the ass. Setting up a wiki, issue tracker, etc to go along with a git server is even more of a pain in the ass.

Well done cloud services make life simpler, and many people will pay for that simplicity regardless of how the internals are built.

Re:Amazon RDS for PostgreSQL by krob on Monday November 18, 2013 @12:38AM (#6752781)
you could always use gitlabs or phabricator and you get much of what you just said is a PITA.
Re:Amazon RDS for PostgreSQL by kennystone on Thursday November 14, 2013 @06:51PM (#6736656)
This is not true at all. Apps on Heroku are built on open source software (Rails, Postgres, etc). You can always decide to host it all yourself without too many issues.
Re:Amazon RDS for PostgreSQL by fat0wl on Thursday November 14, 2013 @10:33PM (#6737542)
How is this not true? It absolutely IS vendor lock-in, just in a slightly less sinister form.

If you add 5 services & then to switch hosts it's not another git push. You have to re-configure each of the services. If you'd done this yourself all along & made machine images it would have been less convenient at the time, but probably cheaper & a good learning experience. There are many other hosting platforms that offer Linux boxes so you could move your whole App/Software layer to another of these companies without much trouble.

I'm not saying Heroku is evil or anything. Yes, they provide a good platform. But I think any web company with a significant customer base would benefit more from the cost savings & freedom of a purer platform than the conveniences of Heroku.

Plus, there are so many configuration issues with their services. I have auto-scaling setup with Adept and still I see these long request-queue buildups now & then. I get the feeling I would not have the same issues with an AWS stack where I have CPU usage monitors that are very transparent & all the networking is trivial.

I still use Heroku as an app server & don't hate it enough to up & move (though a large factor in this is I'm not the one footing the bill, the client is...) but anything I can easily get on to AWS is a no-brainer. Database is one of those things -- a couple clicks to scale up/down every year is all thats really required.

CONCLUSION (cuz I rambled too much): I think Heroku offers scaling/convenience but AWS is just so rock solid & cheap that you can probably just buy larger instances than you need (to compensate for scaling) and have much better performance at the same price. Then you just need to learn how to install your tools & take a machine image as backup. Plus there's a lot of value in learning how to work with machine images that goes way beyond hosting a web app.

Re:Amazon RDS for PostgreSQL by jaggederest on Friday November 15, 2013 @05:33AM (#6738685)
> Plus there's a lot of value in learning how to work with machine images that goes way beyond hosting a web app.

Every minute I spend doing that is a minute I spend not doing things I enjoy. YMMV though.

Re:Amazon RDS for PostgreSQL by fat0wl on Friday November 15, 2013 @10:33AM (#6739952)
Yea I feel you on that but on Heroku I feel like "Every service I add is a per dyno credit card charge that is about to be multiplied by the number of hours in a month". :(

I prefer the Amazon model because you can stick these all on one server & as long as CPU isn't pegged at 100% you're good. I agree tho I'd rather not spend the time figuring it out. For now I only use it for RDS & for services not available on Heroku (some Adobe streaming server stuff).

Re:Amazon RDS for PostgreSQL by simonw on Saturday November 16, 2013 @08:52AM (#6744693)
This is almost the complete opposite of vendor lock-in.

Vendor lock-in is when you write your software on Oracle or MSSQL and moving away requires you to rewrite your whole thing. It's not losing the convenience of "got push" for deploys and having to spend time moving off their hosted versions of open source software and configuring and hosting it yourself instead.

Accusing Heroku of practising vendor lock-in is honestly absurd.

Re:Amazon RDS for PostgreSQL by fat0wl on Saturday November 16, 2013 @10:46AM (#6745108)
IMHO vendor lock-in is anything that makes part of your work process specific to a given vendor. The harder it is to move from one vendor to another, the deeper you are "locked in".

And as a point of interest, I think these days its probly much easier to convert your database than it is to switch hosting platforms (well... in some cases).

Re:Amazon RDS for PostgreSQL by shaikhtabrez on Thursday November 28, 2013 @12:22PM (#6815450)
We started off on Heroku because we wanted something dead simple. The amount of time heroku saved us was an incredible value when we were starting out. I don't think there is any vendor lock in. We just did not switch to AWS earlier because our needs were met really well by Heroku and even Amazon Elastic Beanstalk (for ruby) did not come near the ease of a Heroku deployment. Once Opsworks came around, we invested in deployment scripts and switched because Opsworks gives us same ease of use and greater control of our stack.

What do you think stops you from switching? We had no issues at all - definitely none from Heroku.

We still use PostgresSQL from heroku because it is still a solid service and comes with niceties like dataclips. I should confess that I have not explored the Amazon PostgreSQL offering but I am happy with Heroku for databases at the moment.

Re:Amazon RDS for PostgreSQL by catch23 on Saturday November 16, 2013 @04:22AM (#6744250)
Heroku is great for clients though. When I was a freelancer, I built these apps for other companies that assumed that I would do the admin & hosting. Heroku is great way to just "tack on a fee" for doing the hosting. If they want a cheaper option, they can always do it themselves. Most clients don't care about the savings on hosting..
Re:Amazon RDS for PostgreSQL by avenger123 on Thursday November 14, 2013 @05:36PM (#6736191)
Fair enough. Looks like not a lot of love for Heroku for you.

This could be a nice fire under Heroku's ass to get more competitive.

Re:Amazon RDS for PostgreSQL by eli on Friday November 15, 2013 @10:02PM (#6743378)
Hard to compete with your main supplier, no?
Re:Amazon RDS for PostgreSQL by eonil on Thursday November 14, 2013 @05:45PM (#6736247)
Also Heroku is not available in Japan region. Simply funny.
Re:Amazon RDS for PostgreSQL by sync on Thursday November 14, 2013 @02:03PM (#6734603)
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.

Re:Amazon RDS for PostgreSQL by adrianh on Thursday November 14, 2013 @02:52PM (#6735034)
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 by pallandt on Friday November 15, 2013 @09:37AM (#6739620)
Chiming in with some more appreciation! Great stuff!
Re:Amazon RDS for PostgreSQL by mmcclellan on Thursday November 14, 2013 @01:31PM (#6734311)
Came here to say "This is huge!", found Django creator beat me to it.
Re:Amazon RDS for PostgreSQL by pc86 on Thursday November 14, 2013 @01:09PM (#6734099)
Let me just say that I absolutely love soundslice. It's a great application!
Re:Amazon RDS for PostgreSQL by adrianh on Thursday November 14, 2013 @02:34PM (#6734899)
Thanks! And it'll be even better once I migrate to Postgres. :-)
Re:Amazon RDS for PostgreSQL by rabidonrails on Thursday November 14, 2013 @04:40PM (#6735817)
Wow, Soundslice looks amazing! Excited to play around with it.
Re:Amazon RDS for PostgreSQL by saltyknuckles on Thursday November 14, 2013 @01:46PM (#6734458)
Its actually really really impressive
Re:Amazon RDS for PostgreSQL by coolrhymes on Saturday November 16, 2013 @10:22PM (#6747412)
Good to see another Django creator. We are a proud django startup @kipinhall I couldn't believe my eyes when I read RDS Postgres offerings.
Re:Amazon RDS for PostgreSQL by saltyknuckles on Thursday November 14, 2013 @01:20PM (#6734208)
Hell fuck yeah this is huge!