Uber's Move Away from PostgreSQL

So far is very cool how dramas were avoided regarding to this switch. I think that even more "corporate" entities should switch to acting like Postgres folks, taking it well when people move away from their systems. Sometimes moving away from a system is not necessarily just a technological matter: people get tired of how a given system is designed, of its complexities or on the contrary of its simplicity that does not hide low level details. Certain times the problem is the lack of high quality documentation and information about how to run such systems at non-obvious scale. I even saw people moving away to technologies because they were struggling with their initial stack, and a vendor of the target technology approached them saying "we can help for free if you switch to X". There are certain situations where a system that is not performing well for workload A could be tuned to work well but there is another that can just be used out of the box with success for the same workload. To avoid becoming a super expert of everything is also an option. The thing I don't understand about all this, is the propaganda made by the switchers. Sometimes you see companies almost working with PR firms of database XYZ (the target of the switch) in order to handle the communication. Or blog posts from well known companies blaming certain databases in a way that will be undetected by 95% of readers, but where the problem is, actually, a misunderstanding of how the system works (in part the Uber case qualifies apparently?). So a good rule could be: we have tons of open solutions now, use what you want, switch all the times you want, if you really care blog about your switch, but: 1) Tell about your experience in a subjective way not stressing the shortcomings you saw in your former system of choice as general problems. 2) Consider instead blogging what you are doing with your new system and why it performs well, instead of analyzing while the previous one did not work. 3) If you really want to make a comparative analysis, put weeks of work on it, so that you make the best you can in order to really explore all the tuning and options that were available in the system you are abandoning. If after the post the community will point you in the direction of errors, both correct your old post and make a new post with updates. So I think it's great to see folks with a vibe like Postres are still around, but conflicts could be avoided also by being more soft in criticizing solutions that, after all, kept your business running for months or years.

Uber says the moved to their "schemaless", which means, as far as I understand, that every update will always touch at least one index. Hence am not sure I understand why Robert and Markus are not clear about the HOT vs Non-HOT case; all the updates will be Non-HOT.

The reason for using a particular license at "some company" has nothing to do with a community preferences regarding GPL or BSD.

Not agreeing nor disagreeing with BSDvsGPL theory, just pointing out a flaw in your reasoning.

> "It's human nature"

Rather than making difficult-to-prove statements about humans that imply some sort of just moral backing for behavior, perhaps we should just refer to it as "something [lots of] people do."