Uber's Move Away from PostgreSQL
rhaas.blogspot.com
Uber's Move Away from PostgreSQL
1–10 of 17 posts
Re: Uber's Move Away from PostgreSQL
#2It has been pointed out before, but I'll mention again. It is impressive how PostreSQL community reacted. There was no immature name calling, no blaming users. They analyze the problem, mention possible solutions, admit known shortcomings and so on. This is a community worth being a part of and engineers worth working with.
Re: Uber's Move Away from PostgreSQL
#3It has been pointed out before, but I'll mention again. It is impressive how PostreSQL community reacted. There was no immature name calling, no blaming users. They analyze the problem, mention possible solutions, admit known shortcomings and so on. This is a community worth being a part of and engineers worth working with.
I completely agree. It's human nature to become defensive when presented with conflict with your current way of thinking, and yet here they didn't do that.
I thought that this article was a very well reasoned and thoughtful response to the Uber article and gives me hope that PostgreSQL will continue to improve.
Re: Uber's Move Away from PostgreSQL
#4It has been pointed out before, but I'll mention again. It is impressive how PostreSQL community reacted. There was no immature name calling, no blaming users. They analyze the problem, mention possible solutions, admit known shortcomings and so on. This is a community worth being a part of and engineers worth working with.
I completely agree. It's human nature to become defensive when presented with conflict with your current way of thinking, and yet here they didn't do that. I thought that this article was a very well reasoned and thoughtful response to the Uber article and gives me hope that PostgreSQL will continue to improve.
> It's human nature to become defensive when presented with conflict with your current way of thinking, and yet here they didn't do that.
I wonder if this attitude is correlated with their choice of the more laissez-faire BSD license compared to GPL MySQL. It seems to indicate a less strong personality attachment to the project.
Re: Uber's Move Away from PostgreSQL
#5Earlier quoted context omitted.
I completely agree. It's human nature to become defensive when presented with conflict with your current way of thinking, and yet here they didn't do that. I thought that this article was a very well reasoned and thoughtful response to the Uber article and gives me hope that PostgreSQL will continue to improve.
> It's human nature to become defensive when presented with conflict with your current way of thinking, and yet here they didn't do that. I wonder if this attitude is correlated with their choice of the more laissez-faire BSD license compared to GPL MySQL. It seems to indicate a less strong personality attachment to the project.
The MySQL license was a commercial decision by the company (MySQL AB) so that they could also sell proprietary licenses to businesses.
Re: Uber's Move Away from PostgreSQL
#6Re: Uber's Move Away from PostgreSQL
#7Changing database platforms is a big project, and not something you do without consulting experts first.
More than anything, I'm shocked that Uber eng mgmt didn't reach out to the postgres core team for help first -- as you can see, they'd gladly have helped.
Re: Uber's Move Away from PostgreSQL
#8This article strikes me as more honest/objective than http://blog.2ndquadrant.com/thoughts-on-ubers-list-of-postgr....
Re: Uber's Move Away from PostgreSQL
#9I've had success with bucardo, not sure if they tried that. Going to mysql will pose its own set of problems because both of these databases are not really designed for that kind of scale.
Re: Uber's Move Away from PostgreSQL
#10I've had success with bucardo, not sure if they tried that. Going to mysql will pose its own set of problems because both of these databases are not really designed for that kind of scale.
> because both of these databases are not really designed for that kind of scale
citation needed, because AFAIK that's not true. Implemented right mysql can scale as far a as you want it to.