3 ms·
What do you propose? That every company reinvent the wheel or host everything locally even if it’s not their core competency? Every company has to decide what i
by scarface74 6y ago
What do you propose? That every company reinvent the wheel or host everything locally even if it’s not their core competency? Every company has to decide what its “unfair advantage” is and concentrate on that.
- AriaMinaei 6y agoI think you are jumping to the "What do you propose?" question before understanding the pain point first. You are asking for a solution before agreeing that there exists a problem. This is the "I'll listen to your problem if the solution is convenient" mentality. It's inside-the-box thinking. It holds you back.
- scarface74 6y agoThe opposite of depending on another company to host a service is to host it yourself. The average company of any size has at least a dozen external SAAS dependencies. Do you want to have the expense of managing all of those services yourself?
- mrmonkeyman 6y agoThat's the easy part.
- scarface74 6y agoReally? Have you taken into account the fully allocated cost of the employee to manage it and the hosting cost? Do you have a DR strategy?
- throwaway_pdp09 6y agoWhat is "The average company of any size"? It depends on what you want but managing complex software may be expensive and has some serious economies of scale, which makes a pressure to outsource, even expensively. You can't just brush it off with 'that's easy', it's not.
- mynegation 6y agoAnecdote, but here is a specific situation. Company X has both internal cloud (based on OpenShift) and “public” cloud (Y: one of the big three cloud providers). Application team Z has applications on both, for historical reasons. One of these days application on the internal cloud fails, remediation requires attention from X’s infrastructure team (which is not the same and quite removed from application team), situation is dragging for hours initially and repercussions are cleaned up for several days afterwards. Business is losing money and is furious. Similar situations happens on a public cloud, application team gets a tech resource from Y calling back in two minutes and the whole situation is resolved in two hours. The immediate costs are only part of the picture.
- PaulHoule 6y agoIt goes both ways. There have been times that the control plane blew up in one zone of one cloud provider. I had a least-complexity system which lived in that zone so it kept functioning as if nothing happened. Other people panicked or had their automation freak out for them, they tried to restore their multi-AZ systems, overloading the control plane for the whole region. It's a stressful experience if you feel you can't do anything about it, and sooner or later you will feel it with cloud computing: periods of 8-12 hours where your environment is FUBAR and you are best having some faith they will stitch it back together and walk away from it for a while.
- scarface74 6y agoThe difference is... If my colo goes down. My customers are going to complain and think I am incompetent. If my cloud hosted infrastructure goes down and everyone else is down your customers are a lot more understanding. “No one ever got fired for buying IBM”
- zozbot234 6y agoWhat's wrong with hosting software locally and buying 3rd-party support for the stuff that's "not core competency"? It eliminates a single point of failure.
- scarface74 6y ago>What’s wrong with hosting software locally....it eliminates a single point of failure. I’ll let that just sit there. But you are going to host your own project management software? Your own expense reporting software? Your own email server? Your own payroll processing? Salesforce equivalent? Your own git server? Dropbox equivalent?
- encom 6y agoWhy not?
- scarface74 6y agoA) are you willing to spend the money on servers and staff to maintain it? B) would it have the same reliability characteristics? C) do you have a DR strategy? D) after you spend all that money, did it help you either save money or make money? Did it give you a competitive advantage? Did it help you go to market faster?
- gav 6y agoShort answer: generally it costs more money for worse results. Longer answer: doing things in-house that are outside your core competencies and/or value creation model is a poor use of scarce resources (both capital and human—predominantly management bandwidth) and increases risk carried. To give a concrete example: imagine you need to host your source code repository. You can pay for something like Bitbucket for $6/month/user and not have to worry about it. It’s a price that scales linearly with your team size and is a tiny fraction of their total cost. Doing it in-house: you have to pay for hardware, storage, worry about backups, have somebody support it, have somebody manage the person that supports it, deal with users, find a solution to remote access, and so on. But all these miss the big cost—risk—what happens if the server dies or your office burns down? Nobody used to get fired for buying IBM, nobody now gets fired for buying a popular SaaS product. You aren’t Google, at some point scale changes the equation, but that’s a rare spot to be in.
- z3t4 6y agoThere is a third option: Let someone else host it. Having only one supplier is a monopoly. But if many companies compete about serving customers, you can choose the company with the best service, or if you prefer - the lowest prices.
- scarface74 6y agoNo one company provides all of the services that the typical corporation needs.