Technology
This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.
Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.
Rules:
1: All Lemmy rules apply
2: Do not post low effort posts
3: NEVER post naziped*gore stuff
4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.
5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)
6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist
7: crypto related posts, unless essential, are disallowed
view the rest of the comments
Money. It's a lot cheaper to let somebody else maintain your systems than to pay somebody to create and maintain your own, directly.
Flexibility is a huge one too. Much easier to upscale / downscale.
If you are a small company then yes. But i would argue that for larger companies this doesn't hold true. If you have 200 employees you'll need an IT department either way. You need IT expertise either way. So having some people who know how to plan, implement and maintain physical hardware makes sense too.
There is a breaking point between economics of scale and the added efforts to coordinate between your company and the service provider plus paying that service providers overhead and profits.
If coordinating with service providers is hard for a firm, I would argue the cost effective answer isn't "let's do all this in house". Many big finance firms fall in this trap of thinking it's cheaper to build v buy, and that's how you get everyone building their own worse versions of everything. Whether your firm is good at the markets or kitchens or travel bookings, thinking you can efficiently in-source tech is a huge fallacy.
it is not about it being hard. It simply creates effort to coordinate. And this effort needs to be considered. If you do things externally that means there is two PMs to pay, you need QMs on both sides, you need two legal/contract teams, you need to pay someone in procurement and someone in sales...
I agree with you that doing software inhouse when there is good options on the market is usually not a good idea. But for infrastructure i don't see there to be as much of an efficiency loss. Especially as you very much need experts on how to set things up in a cloud environment and you better look carefully at how many resources you need to not overpay huge amounts.
Except for the larger companies you still need a bunch of trained experts in house to manage everything.
Yes, and they're the company's resources so they theoretically do what's best for the company as opposed to hoping Google or (godforbid Microsoft) does it.
The money gets paid either way, and if you have good people it's often the right call to keep it in house but inevitably somebody read a business book last year and wants to layoff all the IT people and let Google handle it "for savings". Later directors are amazed at how much money they're spending just to host and use the data they used to have in-house because they don't own anything anymore.
There are still benefits - cloud DevOps tools are usually pretty slick, and unless your company has built a bunch of those already or is good about doing it, it might still be worth it in terms of being able to change quickly. But it's still a version of the age old IT maxim to never own or build it yourself when you can pay someone a huge subscription and then sue them if you have to. I don't like it, but it's pretty much iron in the executive suite.
As a result, IT departments or companies spend much more than half of their time - totalling years or decades - moving from whatever they were using to whatever is supposed to be better. Almost all of that effort is barely break-even if not wasted. That's just the nature of the beast.
It's absolutely not. If you are at any kind of scale whatsoever, your yearly spend will be a minimum of 2x at a cloud provider rather then creating and operating the same system locally including all the employees, contracts, etc.
It very frequently is not.
No I meant that Google Cloud is very invasive. Why not to use a more ethical provider?
Why do you think it's invasive? How do you quantify which providers are less invasive?
Because they've never read the terms of the paid for services.
Enterprise Google products != free Gmail.
Lots of comments here conflating consumer google accounts with google cloud.
Google is one of the most privacy invasive companies in the world. And judging by encryption standards, terms of service and privacy policies
Are you sure you've not just read bad stuff without verification on the internet and feel the need to chime in on something you don't fully understand?
Yes. I read Google's policies many times.
Me too as a programmer that uses Google cloud to store government information. Which bit of the policy says they are going to access your data, shouldn't take you long to link it to me if you read them as much as you say. Unless what you're actually doing is spreading misinformation and bullshit.
Bruh, Google doesn't offer any enterprise services, duh. Every single thing they do follows the rules of free Gmail!
Then please, point out the specific policies you are referring to. And don't bother with consumer services. I'm looking for the enterprise services that a business would use. So which policies do you take issue with?
and you know the security standards that are achievable on google cloud entirely negate your point right? their cloud offering is a totally different beast