There is an opportunity here for Amazon to take some of this goodwill IBM/Red Hat is losing. Make Amazon Linux run nicely outside of AWS with (free) LTS. Charge for support for those who need it.
When Oracle messed with Java LTS AWS did Corretto LTS. When Elastic did Elasticsearch license change, Amazon/AWS did Opensearch.
They don't need to support esoteric hardware (at least other than their own).
Yeah, I would think functional/function-based indexes should be mentioned. Add an index or add a redundant column? Almost all of time I would prefer the index.
Of course if your database can't be changed then maybe you can use this trick if there is already a suitable indexed column.
Self-hosted full Atlassian stack (jira, confluence, bamboo, bitbucket) for 6+ years. ~200k tickets. To be honest, it just runs with minimal issues.
Mostly downtime is just upgrades. I can remember a few times we've had to add (JVM) memory as our usage increased. Not sure what we're going to do with the discontinuation of server product line. We self-host to keep source code, etc. more than one configuration mistake (or zero-day) away from exposing it to the world.
We are in the same boat. We are looking at the cloud, but the migration tools are just a pain. I can migrate a project to the cloud from Jira, and it even gives me a report of workflow transitions I have to manualy update/change to fix, which is great.
But then, there is no way to keep it in sync. I have to blow that project away in jira cloud, and migrate it again.
So I Have to hard-cut over projects, on a system that has dozens and dozens of projects, and somehow have people figure out which ones are where. or one really, really ugly night to cut it all over, and hope it goes well.
I'm looking for alternatives, but our team is so invested in some very, very customized workflows, its going to be a pain.
Is there any way to migrate away from Jira, or is it full lock-in? I mean, is there any migration tool or service to Redmine, Gitlab, MantisBT, Trac or whatever?
I think one reason Atlassian was successful is that they always invested a lot of effort in building tools to migrate to their products from any of their competitors (obviously not the other way around).
Having worked on conversational AI (virtual agents/chatbots) for over a half a decade now, I can say that there are large differences in the capabilities of the solutions and the quality of implementations. Some are just bad and unhelpful. Some are very good. I'm personally familiar with several voice deployments doing millions of calls a month. Not only are there obvious cost savings but the calls handled (entirely) by the virtual agents get better average cust sat metrics than human agents on the same set of calls. The first time I saw that I was surprised, but, now it is pretty typical. They absolutely can be helpful even if they are still not near to passing the Turing test.
>Oracle will provide these free releases and updates starting with Oracle JDK 17 and continue for one full year after the next LTS release. Prior versions are not affected by this change.
So, if that had applied to 11, it would lose updates from Oracle in 1 year from now. Whereas something like Corretto is currently committed to Java 11 updates until 2027 [0].
They seem to also be planning to increase frequency of LTS to every 2 years, so, basically assuming you upgrade to next LTS immediately (unlikely in any moderately complex app with deps) you have 3 years of free updates.
In my experience, going from 11 to any version above it is quite trivial. 8 to 11 can be tricky, but I believe even that is easier than it was two years ago (thanks to improved library support).
https://github.com/ben-manes/caffeine