it’s trivial to restrict access to file system and other OS functions, which makes it safer to run other people’s code in your environment
-
-
Make Web Development Easy Again™
-
To the original point of my thread though, I don't think serverless will take over because it is not a universally applicable pattern.
-
It makes some things easier and some things harder. It's a good pattern to apply sometimes, but not always.
-
I love the idea of people embracing shared nothing more though! Curious what the serverless community thinks about data storage in general.
-
So far impression that they try very hard not to think about it, but I'm cynical :-)
End of conversation
New conversation -
-
-
i think there’s also got to be an effect of async-first programming style
-
if you’re shared nothing you’re going to be I/O heavy, so a language that prioritizes async I/O has more inherent scaling opportunities
-
Shared nothing threads use the same async primitives (select, epoll, etc) under the hood. https://www.google.com/amp/yehudakatz.com/2010/08/14/threads-in-ruby-enough-already/amp/ …
-
-
(well, the back-office is, with significant scale - data processing pipeline is a Java app transitioning to Rust)
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.