Earlier quoted context omitted.
> They sell servers, but as a finished product. They sell rack-as-compute.[0] Their minimum order is one rack: You plug in power and network, connect to the built-in management software (API), and start spinning up VMs. [0] With built-in networking and storage.
[flagged]
The Cloud Computer
101–110 of 994 posts
Re: The Cloud Computer
#102Earlier quoted context omitted.
Absolutely. The point of cloud computing is that I don't have to care where something is running and that I (theoretically) have infinite elasticity and can scale in and out as fast and much as I need to. None of that applies here.
> Absolutely. The point of cloud computing is that I don't have to care where something is running and that I (theoretically) have infinite elasticity and can scale in and out as fast and much as I need to. Define "I"? I-as-developer can call an VMware/OpenStack API with an on-prem/private cloud and get a new instance just as easily as calling an AWS API. I-as-developer does not have to worry about elasticity if the…
Re: The Cloud Computer
#103Can somebody explain in a sentence or two what this actually is and what the benefits are?
I'll second that, they should make it clear what they're selling and what they have to offer. Every company should have this in their main/landing page... If I can't understand what you're selling/offering in 30sec, then I'm not interested :-) If you take some time and read around their site you'll see that they're offering a ready to run (turnkey) server. They have everything packed together, they've integrated ever…
Oxide Cloud Computer
No Cables. No Assembly. Just Cloud.
Contact Sales
How much easier can they make it? They clearly want to sell computers.
Re: The Cloud Computer
#104This is actually a pretty big deal. They sell servers, but as a finished product. Not as a cobbled together mess of third party stuff where the vendor keeps shrugging if there is an integration problem. They integrated it. It comes with all the features they expect you to want if you wanted to build your own cloud. Also, they wrote the software. And it's all open source. So no "sorry but the third party vendor droppe…
> They sell servers, but as a finished product. They sell rack-as-compute.[0] Their minimum order is one rack: You plug in power and network, connect to the built-in management software (API), and start spinning up VMs. [0] With built-in networking and storage.
Re: The Cloud Computer
#105Earlier quoted context omitted.
> This really is one of these things where every employee in a cheap cost of living area will say "Exactly, man!" and people in an expensive area will see it differently because it might cap them lower than what they could get. Well the co-founders live in the Silicon Valley area, with their physical HQ being in Emeryville: * https://en.wikipedia.org/wiki/Emeryville,_California
Early stage VC-backed startup compensation is very different from later stage companies or bootstrapped companies. It's very common for founders or early employees to receive a lower salary and receive equity instead.
Re: The Cloud Computer
#106Can somebody explain in a sentence or two what this actually is and what the benefits are?
Re: The Cloud Computer
#107But yes, if multiple teams and they have direct access this rack to provision VMs, maybe yes.
Also - as a developer you don't provision VMs on daily basis. You start a project, you need those resources at the very outset and that's about it?
Re: The Cloud Computer
#108I'm a bit confused about them calling it a cloud computer. The primary benefit of cloud is you spend opex instead of capex. Isn't this moving back to capex again?
When opex is a primary benefit of the cloud, that's specifically for start-ups and other businesses that have little working capital. The actual primary benefit of the cloud for most cloud customers is flexibility - prior to AWS adoption, getting a server provisioned could be a multi-week if not multi-month affair negotiating between devs or operators and on-prem infrastructure workers to get the servers through capacity planning and provisioning. AWS made provisioning so simple, that you could start to set up auto-scaling, because you had extraordinarily high confidence that the capacity would be immediately available when your autoscaler tried to scale up.
But opex is not a benefit of the cloud for heavy/established businesses. Cloud opex is a financial expenditure every month that you can't get rid of and counts directly against your profits. Indeed, the desire for capex in the cloud is so high that businesses routinely purchase Reserved Instances and other forms of committed usage, which allows accountants to treat the cost of the RI as capex and then discount the expenditure through depreciation (to zero, since there will be nothing to sell when the RI expires) over the lifetime of the RI. It is normal and frequent for businesses to make capital expenditures to reduce their operational expenditures over time, thus increasing their monthly/quarterly profits.
Oxide's unique value proposition is to give customers, particularly those with high monthly cloud bills that they have difficulty reducing, the operational flexibility of cloud computing with the profit-improving benefits of capital expenditures.
Re: The Cloud Computer
#109I know price will vary wildly based on how many you’re buying, but does anyone have the roughest ballpark for how much it would cost to buy one (1), or like two?
Re: The Cloud Computer
#110Earlier quoted context omitted.
Nonsense. The operative bit of "cloud" is "provision and de-provision instantly via an API, without much concern for what's going on inderneath", not "lives in someone else's datacenter".
It’s called cloud because it’s not in your own data center. Usually cloud symbols were used in network diagrams to depict systems/networks outside of our concern. Also you could don’t really get elasticity with a system like this. If anything, that would be the operative bit for me.
Hybrid clouds even means devs might not know whether it sits in the corporate data centre or a public cloud, because it could be either/or depending on current capacity.
> Also you could don’t really get elasticity with a system like this. If anything, that would be the operative bit for me.
"You" as in "the organisation as a whole" don't get elasticity. "You" as in "your department" or "you as an individual" do get elasticity.