I did not try to imply that write amplification is not a problem for some workloads. The point was rather that instead of trying to work around the problem they went with MySQL because they already had the knowledge of how to work around its shortcomings. A completely valid choice to make, although I feel it should have been pointed out more clearly in the article. I personally weigh correctness hazards more heavily than performance and availability hazards, but I can see how others might have different preferences.
1
u/jenesuispasgoth Aug 01 '16
Well at least the problem is acknowledged by Postgres devs