Explaining brief a history of edge computing for webapp
Edge Computing for theWebAppragingwind
View Slide
Edge Computing
History of Computing
Mainframe computing- 1960 ~ 1970- Large, monolithic systems- Physical datacenter on-site- Serving via terminals
Server / Client computing- 1980 ~ 1990- Primary datacenter for largeproject and data storage- Working on the network formultiple client connections- Serving via local computer
Cloud computing is- 2000 ~ 2010- Data centers as public cloud platform noton-site- All of the processing and storagehappening offsite in the cloud- Running many of services, Infra, Services,Containers, Workers, Functions ...- AWS, GCP, Azure, ...
Edge ComputingToday
Edge Computing- Ultra-low latency and decrease in bandwidth use- Decrease in server resources- Functionality not only static resources- Mobile, IoT, Apps need for speed
Edge Computingfor the WebApp
Edge Computing for theWebApphttps://vercel.com/blog/regional-execution-for-ultra-low-latency-rendering-at-the-edge
https://vercel.com/blog/regional-execution-for-ultra-low-latency-rendering-at-the-edge
https://www.prisma.io/blog/database-access-on-the-edge-8F0t1s1BqOJEDatabase access on the Edge
Kelsey Hightower'You can host not just images but logic andrun it safely on the Edge, like why now ?'
Innovations for the Edge- Process Isolation- Optimized minimalistic code- HTTP default protocol
Process Isolation- Next process model after container, worker on cloud- Running in sandbox, isolated and stateless- Starting up really fast- Executing optimized minimalistic code- V8 Isolates(Vercel, Deno, Cloudflare), microVMs(AWSfirecracker),WASI(WebAssembly) gVisor, OSv
https://aws.amazon.com/blogs/aws/firecracker-lightweight-virtualization-for-serverless-computing/
https://developers.cloudflare.com/workers/learning/how-workers-works/
https://deno.com/blog/anatomy-isolate-cloud
https://blog.jdriven.com/2022/08/wasi-capability-based-networking/
Optimized Minimalistic Code- Generate highly optimized machine code- low-level incremental computation engine for individualfunctions
https://turbo.build/pack
HTTP Default Protocol- `Web is becoming the computer then the concept of http being themost dominant protocol` - Kelsey Hightower- 0-RTT(Zero Round Trip Time) via TLS 1.3 or QUIC- HTTP/3 powered by `UDP`
HTTP/3 powered by `UDP`https://blog.cloudflare.com/the-road-to-quic/
Edge Computing for WebApp- Using functions on the Edge as like local package- Using server resources on the cache of Edge as like localfiles- WebApp/Functions can be served in compact size as much as decreased- Bring computing power from outside Browsers in a second- Centralized WebApp can be running close to users- ...
Chronology of the WebApp
Image converting WebApp
WAS on Bare-Metal- Using computing power ofdedicated physical server- Physical distance and countare matter
VMs on Cloud- Using computing power ofmultiple instances in a physical- Scale-up and down instantly- Physical distance is still matterbut not count
Function / Lambda- Using computing power on centralizedfunctions on cloud- Computing and virtualization is becomingmore granular- Serverless- Physical distance is still matter but not count
Edge- Using computing power on decentralizedcompact functions on each Edges- Ultra-low latency to function andresources- Physical distance and count doesn'tmatter