29
Open-source and self-hosted enterprise?
(feddit.nl)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Sep 2024
29 points (96.8% liked)
Selfhosted
39241 readers
260 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
I'm going to being contrarian, as is my bit.
I self-host everything and fully believe everyone else should too.
HOWEVER, if your self hosted shit breaks for say, 3 days, how much money is this going to cost you?
For business stuff you really really should determine what your backup plan for 'Oops shit's dead' is well before shit's dead, and honestly, in some cases, maybe it makes more sense not to host everything and have a couple of things that would wreck your business provided by a SaaS company that has a SLA, and on-call engineers, and all that good shit.
Just a thought to keep in mind, I suppose.
Well said, and the 'oops shit's dead' is also in the making. We have the chance to be close to a school so electricity + internet is never down. The time to move to a VPS/other location is minimal, with encrypted backup on multiple locations. Open to suggestions to improve the setup.
Well, a fault isn't just an outage.
You said the other person involved isn't technical: what if say, a database corrupts itself and you're on vacation for a week.
Is the expectation that you'll always be available all the time to fix technical problems?
And, as a failure state: what happens if you simply cannot be reached for that week no matter what. What's the failover plan for the rest of the people involved in the business?
Yeah, the bus factor is an issue to take into account also. I'll need to find someone else to be able to solve those issues.
And then you are basically hiring an infra team to run the services and have the redundancy, and then with salaries you're nearing just paying for software again