Infra is often a financial decision as much as technical.
(reminds me of basecamp exiting the cloud but I know nothing more than that)
Infra is often a financial decision as much as technical.
(reminds me of basecamp exiting the cloud but I know nothing more than that)
Not having the amount of expertise or hours on hand to support it can be another. Shadow labour costs can add up pretty quick and some orgs like offsetting that to the vendor to not overload their people.
Another consideration is how much the tech aligns with your core business. Just because you need it doesn’t mean you should build or run a ticketing system.
Too often there is a lot of SharePoint whiplash and problem “solutions” that grew out of control.
Large orgs don’t always behave rationally and pragmatically when there is self preservation or politics at play instead of being effective at your work.
I believe the question is really high level and strategic and there’s no one size fits all.
Not really, SaaS built specialized automaton to reduce the engineering effort so that they can scale better. Therefore, if the users need to spend 1 hour/day on their infra, the SaaS can spend the same amount time to manage infra for 100s customer.
In some extreme cases, the software run by the SaaS is completely different to what the regular users use. For example, Confluence Cloud Kafka service does NOT actually run Kafka underneath, but a proprietary system called Kora that speak Kafka protocol.