Telecoms, Developer, Manala discussed on Software Engineering Daily

Automatic TRANSCRIPT

Life cycle for edge applications and devices, and then the third one is for future apps that I believe are hardware. Independent voice. Independent cloud. Independent. What are the set of API's that can be exposed in standardized? Right. Both on the southbound side of the drivers. And the physical interfaces as well as the northbound side, which is really around the cloud and the multi cloud infrastructure, right? And those three are technical like to technical one non is what elephant is intending to solve in previous episodes. We've done a lot of coverage over the dynamic between the quote, unquote, cloud and the edge. And this is a really interesting dynamic. You know, like, what kinds of processing do you do on the cloud? What do you want to do on the edge? You know, what are you going to do about the fact that you want to have this high bandwidth connection between these two places, but maybe there's intermittent bandwidth that the edge these kinds of things, but what I understood by reading about LFM edge, the the Lennox foundation's, edge computing, set of projects which will get into some detail, but the importance of the telecoms, and the fact that all of this processing or all of this. Data shuttling is is going across telecom infrastructure. Can you explain the role of the telecoms when it comes to the dynamic of edge computing? That's a brilliant question. Right. Because the moment we classify Najat. Nation requiring storage and compute close to it with a certain Bamut or of latency responsiveness. You do get into the physical barriers of how bitch travel, right? And so at this point what telecom edge or edge, cloud or smart edge, or what the does just to Manala. Jeez. Right. But really what we're talking about is a set of automated, compute storage and software infrastructure that is reciting either at the bottom of the bay stations or on a gateway in in in the basement of a building or our stadium or a little bit further out in a smart central office in a in a neighborhood. What telecoms bring to the table at three things they bring the location advantage. Right. They bring the latency advantage both because of location, but also because of technologies like five G, and they bring the mobility advantage. And what that means is if there's an application connected cars. Economist driving and fleet transportation being the perfect example, if the application requires low latency response with mobility, you do not an enterprise or a cloud provider will not be able to solve that. I so those are the three things why telecom is such a critical player in the edge compute space. And that's why we see a lot of collaboration between telecom players cloudplayer's an enterprise not players. That's that's the mission of elephants and who. Not to sound flippant who cares about this. Like if I'm a developer. Do I care like aren't I just like either? I'm a developer like building something for my factory. You know, my company owns factories. And I'm writing software for the factories or like, I'm maybe I'm writing software that is doing processing on data that has made its way from the factory into the cloud. But in either way, I I work for you know, a candy factory company. Why do I care about telecom infrastructure, or or is this is are these open source projects, which which we will get into our these open source projects are they only meant for the telecom. No, no, they're not meant for telecoms. That's the whole point the projects are bringing the Telecom's cloud and the enterprise were tickles, the dare developers and their use cases all together. Okay. So the three have to operate, in harmony the reason. Why a developer and enterprise cloud. There are telecom player should care, right. Is what you described as a analytics sitting in a factory going into a cloud. That's that's I am not today. That's not an edge. That's not an edge app..

Coming up next