That's It, I'm Done With Serverless*

What is the edge runtime?

Hey, you are aware of provisioned concurrency on AWS lambdas? Cold starts are a relic of the last decade and are no longer a thing.

So no ffmpeg @ edge ... shouldn't v8 isolates support wasm? Technically able to execute rust binaries?

such utter crap

awesome video, grateful to have this knowledge for free!

I really like how you give an explanation with a visual diagram to support it. It's really helping me understand some of the more infrastructure-side tech.

Thoroughly absorbing, isn't it? For a continued absorption, consider a book I highly esteem. "AWS Unleashed: Mastering Amazon Web Services for Software Engineers" by Harrison Quill

Finding this informative? Dive deeper with a congruent book I hold in high regard. "AWS Unleashed: Mastering Amazon Web Services for Software Engineers" by Harrison Quill

And the first thing I do is to run Prisma. 😂

With all troubles of "serverless", isnt it better to just use "servered"? Keep process running on server to avoid cold start, have infinitely faster connection to database on same server/cluster. And request time from user to server is same as regional edge

just deploy all your services to a single region and proxy the final response with cloudflare at the edge

If you think 300ms req times is crazy fast speed, you better not ask what I have for req times. 300ms is not great, it's just barely acceptable.

Hello! Thanks for video! Wonderful diagrams! Which software did you use to draw it?

Theo the type of guy who is so convincing in every single video that he makes me doubt my stack forever 😂

I'm very interested in what a harelip magician thinks about software architecture.

This is a fantastic video. Really wonderful job explaining the trade offs.

lol, loves javascript base shit but hates slow apps

Idk I deployed my own cloud on premise and I find putting stuff directly on Linux is less cumbersome and less complicated than all that serverless or edge or whatever stuff.

I can’t control cloud providers I can control my servers. I can’t own cloud providers I can own my servers

i hosted google cloud run for 1 month with 4G ram and 2 cpus, i was charged for 130 euros, barely 20 request to my api xD

What is the tool he is using to paint and write?

Prisma has an edge runtime now. Even at the time that this video was posted prisma had it - yet you claim that prisma can't run in edge.

can web assembly be used to solve the c++/rust incompatibility limitation?

"I want my ideal stack to be serverless." - Ryan Dahl

Idk why i cringe every time i hear someone say running on the edge to avoid spinning up a linux box. Someome somewhere spun up a linux box for you to run your edge functions on...and youre paying for it. Its why lambda costs a lot and im sure once initial custlmer base is built for edge applications they will increase their prices and no longer be loss leaders

I don't understand? If performance and user experience is the most vital over networking, this is solved, it's called online mobas, millions of random users connected in a random instance each second where every game actions for each user is less than 10 - 20 ms at all times and emited to each other user in real-time bi-directionally, based on randomized input, and u worry about the hardships of getting a a few packets of json somewhere within 1000ms, okay..? Why try to re-invent this? Sometimes it's better to talk less, step backwards and listen more. A lot of the answers are already there in between the technobabble and hypenoise

Thank you for saying "I couldn't care less" 🙇‍♂

So first up you are wrong. So much to address so I will respond later when I land.

Descriptively speaking, I'd say that edge is better defined as the location rather than the runtime. That's not to say that your video shouldn't be hyping up the characteristics which are typical to edge products, just that people will run into less mental adjustments if they define edge as just the location. For example, some companies buy edge services from places like at&t or tmobile where they install their own compute close to the cell tower. No special runtime and no savings on devops.

Edge. Edge functions. Global edge vs regional edge. Polyfills, no support for binary. All tested with one query. No thanks.

if serial queries are the issue, why not something like GraphQL (or batched RPC of any kind)? that would give you the best of both worlds no?

this guy is awesome, subbed. this is great clean no bs info

I think the main problem I see with this is the reliance on javascript. Its a horrible language in my opinion and there are much better technologies for writing good code. The only thing it has going for it is that it can be interpreted which is why using it for "edge functions" makes sense. But if you're really talking throughput for an application you don't want to rely on javascript for that especially once it becomes more complicated in the business domain sense.

elixir/erlang? You don't need to use edge or k8s just let BEAM helps you ^^, and you are already using BEAM at your router and load balance, probably.

I think you shouldn't be using the word "edge runtime" to refer to Chrome's V8

You're so deeply incompetent, man.

got to love how a bad implementation(lambda) gets renamed as a new technology(edge)

to me GCP containers is the most flexible.. the closest thing to serverless containers. serverless is great if you can restrict your self with what you use.

Edge is also used to talk about edge devices. For instance, whether or not a computer vision model is handled online somewhere, or on the physical device, or the "edge device" or "edge processing"

65c per million is a good deal

no thanks

What presentation tool do you use to explain all about serverless? quick drawing is what kept my attention when you were pointing out the subtle differences between serverless vs edge. Kudos.

Aka, go monolithic and learn how to properly structure your programs. Got it.

Who wants to bet Theo will be using Kubernetes some time next year?😅 These new age devs crack me up. Get back to the basics!! We shall always be going around in circles and eventually come back to what was done in 1995!!

You can be done with Serverless, but it doesn't mean that Serverless is done with you.