Re:So, you want to deploy on the edge?
by bradenb on Monday July 31, 2023 @11:34AM
(#36944186)
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.
[ Parent
| on HN ]
Re:So, you want to deploy on the edge?
by weird-eye-issue on Monday July 31, 2023 @11:35AM
(#36944207)
That's a terrible "definition" of edge
I'd love to hear a better one. Care to comment?
Re:So, you want to deploy on the edge?
by weird-eye-issue on Monday July 31, 2023 @08:19PM
(#36950720)
To 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
It'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.
Not 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.
I 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?"