This is always trotted out and it's, by this point, a completely content-free thing to say. Short of removing yourself from the economy and society in general to live off potatoes grown in your own dung, you're going to rely on some external services and the fact that, for the most part, the parties you do business with will behave responsibly. When they behave very irresponsibly, unpleasant things happen and people quite reasonably complain.
* Malware detection?
Isn't that pretty must how most malware detection works? Sure they use the cloud to pull periodic updates but the software itself is self hosted * Customer support software?
I've lost count of the number of solutions available to self host. Both free and commercial. * Website uptime monitoring?
While there is a strong argument for hosting that in the cloud, there are umpteen solutions for website monitoring. * Accounting software?
I didn't even realise running accounting software as a service was now a thing! * Email delivery?
Fair enough, self hosting email can be a massive headache. Less so if you run Microsoft Exchange (one of the few things Windows actually makes easier than it's Linux / UNIX counterparts). You can even go for a hybrid approach and self host the mail server but have a mail proxy between your server and the outside world - so you benefit from spam detection as a service while still hosting your own mail.I'm not going to argue that one is better than the other when it comes to SaaS vs self hosting. But people in here seem to have very short memories when arguing that self-hosting isn't at all viable. In fact I have personally supported all of the above in self hosted versions in the last couple of years.
I also have the experience of managing many of these services, and I therefore know just how much more productive you can be when you don't need to do it yourself.
Of course there are trade-offs; business is nothing if not a game of tradeoffs. We're just talking about what is optimal.
[1] Not to mention how much more stable and secure; Self-hosting can involve huge security and reliability risks.
I don't believe what is optimal can be generalised like that. "Optimal" is going to be specific to the business in question. Which is why I'm a firm believer of leaving all the options on the table.
> Self-hosting can involve huge security and reliability risks.
In fairness so can the cloud. I personally don't see difference as 'risk' but more 'responsibility'. Some of the places I've worked have been PCI DSS and Gambling Commission audited so we had that responsibility already. Self hosting a few other resources didn't really add much extra in terms of our security responsibilities. But the case would be very different of lots of other different types of businesses.
It's worth reminding ourselves that the root comment was an absolutist assertion about the folly of outsourcing.
So the discussion is easily resolved: don't be absolutist :)
Even that strikes me as a mischaracterization, or, at best, taking just one statement out of context.
It was an assertion about the folly of relinquishing control, not being prepared for that lack of control, and thereby subsequently suffering a prod outage.
Yes, any of those sounds like a good enough plan B. You don't need it to be perfect, just good enough to avoid getting stranded in a pinch. Then you can start shopping around for someone who does that one little thing much better than you do. That way it no longer is a show stopper and rather just an optimization problem.
For starters, most smallish companies I know of use housing for their servers. So, they actually do own the hard metal servers and have full access to them. Both over SSH and on the console for debugging purposes. The housing provider generally replaces HDDs in case of disk failures. naturally, you're still dependent on electricity and internet, but even that can be mitigated by spreading your servers across several locations.
All of that is obviously possible with AWS, GCP or other VPS hosts, but doing it yourself is not that much harder if you've got an experienced ops person that wants to bother with all of that.
but i repeat... Its often not worth the time investment to get that system properly set up. Just renting VMs or going straight into dockerized microservices is an increasingly better alternative
Your local restaurant going out of business is no reason for you to starve to death, you just go to another one, or to a grocery store, or indeed grow your own food if you're in some post-apocalyptic world or got no money... but somehow a service provider going out of business is reason enough for your production to stop? No, just no.
I don't think anyone is suggesting never to outsource, or even that the answer to "build vs. buy" is always "build".
The point is not having a critical dependency on a single vendor.
I don't think anyone is even saying "never", either.
The question is one of risk.
The risk of your tax accountant "going down" (or being crooked or something) is sufficiently low, and the cost of making that redundant is sufficiently high, that I don't think anybody does that. This could even apply to general accounting software, though one might argue that's not critical in the same way and/or more easily replaceable.
There's a sibling sub-thread that essentially implies, if not outright states that there's no choice but to "buy" in "build vs. buy". Although it may be true that building is no longer a practical choice due to time/cost, under certain circustances, it by no means eliminates the risk if there's only one vendor.
It's also a decision that can end up having tremendous costs at scale, if not re-evaluated, especially with even a soft version of vendor lock-in, like AWS.
you did not include "so much that if it goes down it would cause a prod outage" in your quote, which is why the strawman claim was put forth.
This is yet another strawman. The original commenter found it "silly", which, I agree, was a poor choice of wording.
Perhaps "overly risky" would have been better. I don't know. I just take the most charitable reading, per the guidelines.
It also comes after an exhortation to have a contingency plan, so it's at least implied that the "silliness" isn't inherent merely to the dependence but to the dependence without such a plan.
> in many, it's a completely sensible tradeoff
Is the tradeoff actually considered, though? Or is there just an automatic "we're not a nuclear reactor" decision process?
> is 100% uninteresting
Were that true, I doubt there would be replies. This is not one of those traditionally emotional/political issues.
> Including or not including 'in prod'
I (again, charitably) read "in prod" as a metaphor for "business critical". I'm sure we can all come up with examples, even in Internet companies, where one does not necessarily mean the other (or vice-versa). In the instant case, it seems to apply, so it made sense as shorthand.
> It's just lazy grousing.
I would agree if there were no built-in suggestion on how to avoid the problem at all, but there were.
Just because the point has been made before doesn't make it any less valid, until it has been refuted.
Only if 'strawman' means 'thing I disagree with'. The comment says such a dependence is bad and how you have to prepare for it with SLAs or whatever. This isn't universally true at all.
I doubt there would be replies.
A lot of really boring, trite things generate piles of replies. That's why they should be avoided.
Just because the point has been made before doesn't make it any less valid
The stated goal of the forum is not 'an exhaustive, if repetitive collection of generically valid things'. Remember that time you wanted to print something and the thing just wouldn't print? That's bad and annoying. It's valid that it's bad and annoying. We probably don't need to talk about it in the general sense every time it happens, though.
Only if you pretend there are no companies that do in fact responsibly nail this stuff down. There's plenty. Your argument seems to be that nobody does it because it's hard.
There are pretty solid SLA's for that. We provide some services as kind-of-saas but the SLAs are watertight.
Usually in those kind of sla's you can't sell the company (or move assets) without guarantee of delivery of the contract. In some cases they (the contract holders) even own you if you screw up and go under.
I'm curious; what would you have these companies do in such a scenario? If 100% uptime is impossible then what you seem to be suggesting is that people should never use third party services or if they do use them they must not be in a critical path.
Are you suggesting everyone should do everything in house?
If you have to use non-free software, buy software, not services.
If you have to buy services, always have a well-tested fallback path for when that service is not available.
This was in order of preference. If you can, use free software that you can fix and support yourself if need be. If not, buy the software and run it yourself, so you can at least control its operation. The last option is to by SaaS, and if you do, you need to have contingency plans in case it goes away. You should take this risk seriously, and factor it in to your decision when buying SaaS, and invest the engineering resources to make sure you aren't overly dependent on it.
What I'm suggesting is that people should use external services for their lower costs, better performance, or extra features, not to 100% depend on any of them.
There is a popular C# package called Polly that has all sorts of fault tolerant strategies.
https://github.com/App-vNext/Polly/wiki/Transient-fault-hand...
In this case, use a Fallback strategy that responds to an API failure with some type of generic success response.
So... what was the Service Level Agreement? and the Terms Of Service?
People get all hyped by -aaS stuff, but services do go down, and if you aren't the one controlling when and how they will go up, then you better have a contract with the Service Provider on some terms you like.
Even then, prepare for when they go down, because they will sooner or later, for shorter or longer periods of time.
I find it silly to rely on some service, any external service, so much that if it goes down it would cause a prod outage.