How can you read Uber's writeup and support and recommend postgres more each release of every product?
Seems like every release notes there is a section advocating how limited and terrible MySQL is and switching to postgres, for all products.
In some cases, MySQL isn't even supported, such as in Data Center product.
What does Atlassian know that Uber doesn't?
Disclaimer: This is my personal opinion and reflects much of my past experience with MySql (roughly 15 years or so). It is not an official Atlassian position, and as I no longer work on JIRA Data Center, I can't really speak to what it going on or what their plans might be for future support of any database.
I'll just call out a few specific points:
In short, we don't have to know something that Uber doesn't to come to a different decision. We are not the same company, and we have different requirements and considerations than they do.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events