18 ms·
My takeaway from this is that a lot of people disagree on what "edge" is. IMO, "edge" is the furthest resource that you have some computational level of control
by bradenb 3y ago
My takeaway from this is that a lot of people disagree on what "edge" is. IMO, "edge" is the furthest resource that you have some computational level of control over. Could be a data center, could be a phone, could be an IoT device, could be a missile.
EDIT: I think I'm realizing people will disagree with me because I have a different perspective. For my use cases, my data comes from sensors on the edge, and so for me, I want my edge computing to be as close to those sensors as possible.
- weird-eye-issue 3y agoThat's a terrible "definition" of edge
- bradenb 3y agoI'd love to hear a better one. Care to comment?
- weird-eye-issue 3y agoTo me edge is when you are doing most computation and data retrieval required for the given request in a data center close to each user. How to define close? Probably when you have at least several dozen POPs spread out across the world
- hahn-kev 3y agoIt's actually really helpful. Looking at a lot of js frameworks I thought I understood what they meant, but now I understand that the term is actually pretty ambiguous.
- paxys 3y agoNot quite. Nearly every service out there has computational control over the end client (whether a mobile app, browser JS etc.), but very few are focused on edge compute at that level. It is more helpful to think of it in terms of a traditional client-server architecture, where you want to move the server as close to the client as possible. This covers 95% of what people mean when they say edge compute.
- bradenb 3y agoI do see your point, and I agree that covers most cases, but can it really be a definition if it doesn't cover all cases? Are just talking about a distinction between "edge" in an architecture vs "edge computing?"