I doubt that day will ever come without a significant number of potential customers stubbornly opting to go it alone with DIY on-prem alternatives (or at least somewhat SaaS-less - e.g. turnkey-on-IaaS or similar) in the interim. Though I guess that "stubborness" might become more likely as more & more stagnation & inflexibility of cloud SaaS reveals itself to customers over the coming years.
My company's recently been pushed off JIRA on-prem to their cloud offering & the migration has already been an absolute travesty. Any gaps there might have been in the near-universal hatred of JIRA have been thoroughly wiped out by now.
edit: and in fact the DC edition is still an option.
I meant 180, of course :)
But yeah, I think this is more dipping a toe into the water. They seem to be focusing on entirely new products with a reasonable small scope. It's interesting to see it happen, though, and they're moderately influential.
If ”cloud” was available in the 90s, I doubt that self hosting would have been as popular. Not saying its a wrong choice, just a matter of convenience.
Convenience doesn’t matter. The manager will say that SaaS costs half as much and then we get the direction to move.
When the pendulum swings to “On-Premise will cost half as much”, we will get the direction to move back.
The core diff between on-prem and cloud isn't where the data is hosted. It's that in one case someone else handles UNIX BS and in the other case you do. Get a MacOS-equivalent level of usability for servers in a form that isn't rent it by the hour, and you could see such a migration, but what's the incentive for anyone to build or support that when people are willing to pay so much for cloud services?
Is it the need to CLI? Or just the number of knobs that you can frob? Too many choices?
Interested in how such a server system might look.
To compare, try comparing the docs and GUI help you get deploying a simple serverless app to Lambda+RDS vs configuring a Linux box with systemd, apache/nginx, SSL termination, postgres, borgbackup or whatever other stack you want to use. The difference is night and day. The systemd docs alone are classic Linux BS culture. UNIX sysadmin is complicated in very fundamental and deep ways for people who don't have a gray beard. I know how to do it but I don't enjoy it, and I had to recently teach a friend of mine how to do basic tasks. He's a pro software dev with years of experience incl at Google but sysadmin was never something he needed to do. Luckily now ChatGPT can help a lot with the missing usability.
I think the documentation aspect is often overlooked. Even RedHat's subscriber-only documentation is ... quite dense, and yet, not very deep.