3 Burst results for "Horr- Oku"

"horr  oku" Discussed on Software Engineering Daily

Software Engineering Daily

02:45 min | 3 years ago

"horr oku" Discussed on Software Engineering Daily

"Some questions about other markets. There are a number of second layer cloud providers. So I've talked to some companies recently like spot in st- or Zeitz or horr- Oku. How do the margin profiles of second layer clouds compare to those of base-level clouds like AWS, I do think that you're asking the right medication? And the right meta question is is this a winner take all market like his era enough scale level moat is enough of a scale level moat because you have his ability because you've got the economies of scale that you end up becoming the next generation telcos. So what pretty much any economist will tell you is that if you have an economic system or the incremental cost of adding another user converges on zero this is absolutely the case with telcos, right? Then you'll end up in a monopoly situation. That's just basic economics has nothing to technology right at the incremental cost of. Adding that additional user convergence on zero you tend to have monopoly situations. And then the question is is that the case for for these large clouds now, it seems to be that clouds can actually differentiate by the way that services a commodity service. Right. And that's something that anybody can offer that service. It seems like the the clouds can differentiate an ad value. I mean, the workloads at run on Azure, acts you tend to be quite different than those that run on Amazon or digitalization if so we're we're investors in digital ocean. Also tends to be much more developer focus different types of workloads. And so I think actually you may end up in a situation where you can maintain margins through differentiation and through fragmentation of the not the customer base, but the use case base. It was interesting. We used to sell them the multi cloud environments all the time, but multi cloud didn't mean the same workload went between clouds, which I think is one of the biggest misunderstandings on the planet. Right. And like just because someone is multi cloud doesn't mean that they can actually arbitrate clouds. It just means that they use multiple clouds for use case that's best suited. And if if you maintain that, I mean, this is this trillion dollar markets all of IT. Going after. Yeah. Then you can think that actually there will be a fragmentation they'll be differentiation. If that's the case you will be able to maintain margin. But it's early to say that for fact, you could also go back to the taco gays and sitting actually everybody's gonna offer the same thing. The incremental cost betting users going to converge on zero there for the largest one will win. And right now that looks like that would be as on. Why hasn't there been a company that does this arbitrage between different cloud providers? Will so many have tried. Yeah. I've been very close to a number that have tried. And here's my view, my view is because it's not really solving customer pain point. And if that's your primary value. I don't think you can build a successful company. Now is the secondary value. It's great. But I don't think you can sell on that alone. So how do you save money on Amazon the best.

Amazon AWS Zeitz horr- Oku developer trillion dollar
"horr  oku" Discussed on Software Engineering Daily

Software Engineering Daily

04:10 min | 3 years ago

"horr oku" Discussed on Software Engineering Daily

"Bonetti, it can be Amazon ACS very soon gonna be supporting dockers, warm or hassle. Nomad any scheduling platform four containers that you wish and then once as contemporary scheduled the computers, basically abstracted away from you equal scale it will kill zero will scale to whatever copies of of of computer, you need automatically. You don't have to do anything in donate to manage the M's jumped by security patches or fetches a already done in the background by by ocean. And basically gives the developers service way you manage their containers in also very very reasonable pricing of computer, they can on lock as they scale the experience of deploying a container on your product. Ocean. It seems quite similar to deploying a container on an AWS far gate or as Azure container. Instance. These are these long-lived container instances, the server service containers, how do the containers that you're spinning up for people on ocean compared to these container instances that the cloud providers offer. So I think we're hitting a spot where we basically offer the same service like like Ozzy container instances, the or. And a just a matter of like how efficient we are in acquiring the underlying computes and our goal is to be way more efficient that any other provider in acquiring the compute underneath of the container. Right now, I find these container instances so interesting and so useful because I've been a longtime user of horr- Oku and her Roku is as far as I know just giving you a container it's been giving people containers for a very long time since before containers were trendy and they're called Dyno's on her Oku and heroic is made a great business out of selling Daigneault's to people because that's all you need often. You know, many people who are hobbyist developers or even at a large company and they wanted to use her Roku. They can spin up their entire application is just some monolithic application that just runs in a long lived container. And and that's great. That's what a lot of people need. So that's what AWS and Azure have been offering with this far gate and container instances products respectively. And I was talking to you about this. When we were at qb con, but it surprises me that there's not more excitement around the idea of these low cost cloud provider container instances where you can just spin up your monolith in standalone container people see more excited about the idea of managing a Cooper netties cluster. When in fact, like why would you wanna be a cluster operator? You could just be a an operator of your application. Abstraction? Why is that why do people want to manage their coober netties when they could just manage their application in terms of these container instances, you know, different. I couldn't agree more. I think you right in terms of also its greatest you how what he Roka did like becoming so trending now. And also if you go like that and look at Google app engine, which is basically the same thing. Equal. That's true. And ready for not yet. So and I think this is like the strength of eight of US, which they are actually meeting the market, whatever the market needs death. So they will not introduce like, you know, some spaceship when you you just need like a regular car. And I think that that's a big thing for Amazon and right now, he's becoming popular because people like did that you know, runway. Like, hey, we knowing what is container. Okay..

dockers Bonetti Roka US coober netties Amazon horr- Oku Ozzy Google Daigneault Oku Dyno
"horr  oku" Discussed on Learn to Code with Me

Learn to Code with Me

04:31 min | 3 years ago

"horr oku" Discussed on Learn to Code with Me

"We're doing the tire thing product really is understanding the higher flow of an entire us experience. Not just you know, how it looked. But also the functioning, you know, and that's why I love this company so much because I've been trying to get into a role like this ever. So to be here. Now, I'm like, oh my gosh. I can't wait. I'm gonna. Work on this. I'm gonna work on that. I think I'm kinda like stretching myself in but to have the possibility to work on different aspects of the component lists that we have is on those things out in sketch, and then going into, you know, visual code and coating those things making sure it's Billy meat for web. Sanders says Billy standards and Ben passing into developers. They don't have to think about that stuff that we still own that entire us experience is everything to me. I love it. So is there a separate user research team, then okay? Yeah. We don't do that part. Thank goodness. Because again, I know at some companies like product designers can be really involved in like user, research and user interviews, and and all that. But okay. So you there's a there's a separate user research team. And they do what they do that. And they then they pass that knowledge off to you, you guys, exactly. So right now because. Hiroko went Celts for. Gripe this so Heroux challenge more sue the umbrella, though, it has a lot of brands underneath this entire parent. Brin those worth heroic with his own little island and for a long time. We've been doing our own you the research and things like that. But because we're trying to mesh together and become one brand. We're starting to branch off with Salesforce, you X researchers and a screen to them. Our use case was sometime doesn't always come off correctly. Because. Designing for developers. Designing for regular user is totally different. You know? Yeah. That's a really that's like such a good point. And you're at horr- Oku. You're designing developers. Yes. Yeah. Whereas I know Salesforce acquires tons of different companies in I'm sure somewhere more technical than other user base more technical than others. But yeah, that makes sense. I didn't even really connect those dots. But like the like who you're designed for so important but continue so so yeah. So like with Phil towards their users. Are they're not really developers. They're just people who use his drive drop platform at creek apps or applications versus with the velcro. I mean, that's the whole new use case developers. Would I've noticed with our developers is they will create. Let's say the designers broke something something doesn't work. They will create a a run around or walk around on that issue. And created entire new flow for themselves to get through with that they all create their own passed their own happy path. So it's kinda like usually when you have users. They'll call in complain about it develops never complaining. They just make a solution was so funny. Oh my gosh. I actually was doing at my last job, which would do use your interviews a lot, and we would watch people use the product, and we would sometimes have people on or do them who were like developers because you could use the product as developed resume user zero power editor anyway, but like washing developer use it. They were so fat. I couldn't follow them. They don't and they all they build things on top of it. And I was like they do that. I was like it's like it is not a normal user like the norm. You know, like the the average person watching them use is so different than watching a developer us something. Yeah. That's really funny. Yeah. Sells for as the U X. Researchers can't always help us of may can do certain things. But sometimes I feel like we probably need to still on that space a lot more than we are currently of because they only know the normal user versus our users of this totally like leftover them yet Salesforce use your could be like an account manager sales United States, Salesforce and your users are yeah. Like engineers or start up CTO's or something. So yeah, that's really that's really interesting..

developer Salesforce us horr- Oku Hiroko Heroux Billy meat CTO Sanders Phil account manager sales United S Ben editor