Earlier quoted context omitted.
I guess that means "No, it's an unofficial, third party toolkit".
So's jQuery, but that hardly stops me from using it. Unsure as to the point you're trying to make.
Amazon RDS for PostgreSQL
141–150 of 246 posts
Re: Amazon RDS for PostgreSQL
#142Earlier quoted context omitted.
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.
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.
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
#143Earlier quoted context omitted.
I guess that means "No, it's an unofficial, third party toolkit".
So's jQuery, but that hardly stops me from using it. Unsure as to the point you're trying to make.
1. An additional potential point of failure 2. The core software (a DB, in this case) can (and probably will) evolve independently of the third-party tool--thus introducing an additional layer of maintenance problems.
I'd argue further--and this is of course just an opinion--that such a basic feature as this ought to be supported out-of-the-box by anything that claims to call itself a "database" in the sense that MySQL does.
Re: Amazon RDS for PostgreSQL
#144Earlier quoted context omitted.
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.
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…
This could be a nice fire under Heroku's ass to get more competitive.
Re: Amazon RDS for PostgreSQL
#145Earlier quoted context omitted.
Some engineers I worked with went and interviewed people at various San Francisco startups about their experiences with their databases. The MySQL startups tended to say "We love MySQL. We've gotten in the habit of taking an hour or two of downtime in the middle of the night every week to run all of our schema migrations, and we've had to build our process around that, but one we had it in place, everything's been fi…
pt-online-schema-change from Percona addresses this particular point with MySQL nicely for us, incidentally. We use their Percona XtraDB Cluster fork and are quite happy.
Re: Amazon RDS for PostgreSQL
#146Will anyone please explain the tactical reasons why PostgreSQL won? It's pretty obvious it has. I've basically ignored the database wars for a few years, so it's kind of interesting to see that everyone's using PostgreSQL now.
Re: Amazon RDS for PostgreSQL
#147Useful tool to migrate from MySQL to PostgreSQL : https://github.com/lanyrd/mysql-postgresql-converter
Re: Amazon RDS for PostgreSQL
#148Earlier quoted context omitted.
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.
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
#149Will anyone please explain the tactical reasons why PostgreSQL won? It's pretty obvious it has. I've basically ignored the database wars for a few years, so it's kind of interesting to see that everyone's using PostgreSQL now.
You must be joking right? Either that or spending too much time on HN. PostgreSQL has won in the same sense that Golang or Clojure have won: in frequency of frontpage HN articles.
And even though I love PostgreSQL (and was working with all major databases), I still think that the real winner is sqlite :)
Re: Amazon RDS for PostgreSQL
#150Earlier quoted context omitted.
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.
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.
& it would be louder if the rest could figure out where to put the custom DB URL parameter ;D