Please fix the scrolling under mobile Safari, it has no momentum.
[deleted]
What the f*** is the edge?
11–20 of 188 posts
Re: What the f*** is the edge?
#12I presume that nobody sane is sending critical self driving car decisions to the cloud.
It was only used as an example of something you CANNOT do with such high latency. It was not implying some company out there is actually using a high latency server for real time processing
Re: What the f*** is the edge?
#13Wouldn’t a PHP app with app servers in locations in many POI then connected to azure cosmosdb essentially feel like and act like”the edge” to a user.
Nuxtjs and nextjs are “the edge” apps. But the server being centrally located especially for global ecommerce needs to go the way of the dodo.
Shopify being one. Some plus clients are near $800,000+ a year. Yet still no database or app servers outside the US.
Re: What the f*** is the edge?
#14> This front-layer of computing power is also referred to as "fog computing" or "dew computing".
The bit about self-driving cars talking to a server to make split-second decisions is laughable but this right here just makes you want to flip the table.
If you're requirements are so extreme that you need to be on "the edge" you can do that today, it's called client-side development.
Re: What the f*** is the edge?
#15We (Cloudflare) have largely stopped talking about the 'edge' for some of the reasons cited in the article.
1. No one actually knows where it is or what it means.
2. It conjures images of classical ‘edge compute’ use cases like the self driving cars in the article. Those use cases tend to be exceptionally specialized (or just silly).
3. Edge implies a core or origin exists, and maybe it doesn’t need to.
We would rather imagine a world where we embed the compute directly into the network, putting hundreds or thousands of points of presence within a few ms of everyone on earth. We imaging moving all the compute and storage there, not just some fraction which needs ultra speed. If it is easy to run code close to your users, and it’s affordable, there’s no reason everyone shouldn’t run everything as close to the consumers of the Internet as possible.
Re: What the f*** is the edge?
#16We (Cloudflare) have largely stopped talking about the 'edge' for some of the reasons cited in the article. 1. No one actually knows where it is or what it means. 2. It conjures images of classical ‘edge compute’ use cases like the self driving cars in the article. Those use cases tend to be exceptionally specialized (or just silly). 3. Edge implies a core or origin exists, and maybe it doesn’t need to. We would rath…
A fully mesh P2P computer cloud would be magical. Everybody is the edge that way :)
Re: What the f*** is the edge?
#17This seems like an exercise in quickly ascertaining what kind of audience you have. If you are talking with someone who needs to feel like they are buying "the edge" or whatever, adjust your sales pitch. Also, if you start off with a buzzwordy pitch and realize you're speaking with an engineer, switch to a more technical approach.
Re: What the f*** is the edge?
#18> real-world transmission times between e.g. London and San Francisco end up at around 150ms. That's [...] a catastrophe for self-driving cars needing to make realtime decisions. Why in the world would/should a car in London be relying on a cloud computer in SF to tell it how to make real-time decisions...?
Most of the teleoperation companies at the moment. As far as I know. Worse still many are intending to gang onto the primary cellular infrastructure to perform the function. Which makes everything worse.
It's fine if you are going to have your cars remotely controlled with a latency > 150 ms while they operate autonomously as things happen in a shorter time frame.
But the other way around seems insane.
It's reminiscent of the way people have switched from "human drives, computer deals with emergencies" to "computer drives, human deals with emergencies" as though it was no big difference.
Re: What the f*** is the edge?
#19> When e.g. AWS Cloudfront, Amazon's Content Delivery Network talks about "Edge Caching" it simply refers to the Amazon datacenter closest to whoever requests the site.
Kind of? If by "datacenter" they mean the things they said earlier that AWS had 18 of, then no, not really. There are many more Cloudfront points of presence that there are AWS regions (over 100 of the former). In practice unless someone lives very close to a proper AWS region (like I do here in DC), odds are there's a Cloudfront PoP much closer to them than a "datacenter" (i.e., AWS region).
Re: What the f*** is the edge?
#20> "Edge Caching" it simply refers to the Amazon datacenter closest to whoever requests the site
I can't speak for AWS, but for GCP there are many more Edge and CDN points of presence than there are datacenters:
https://cloud.google.com/about/locations/ (flip to Network tab in map)
And in Google's case "Edge" simply means where you exit the public internet and get on to Google's own network:
https://peering.google.com/#/infrastructure
Although there are also "edge nodes" (caches) located within ISPs outside the Google network.
Disclaimer: I work at GCP, but not on networking.