Is azure functions comparable to those concurrent processes? Not sure how Microsoft runs this on their side, I always assumed it was based on kubernetes pods, they have max runtimes of 15 minutes and are instantiated by request. I'm a c# dev who mostly has worked in kubernetes environments where people thought in terms of "microservices" but someone at work introduced me to eventsourcing, cqrs, feature slicing and high cohesion services. Then it evolved into running each feature in its own process, and now he introduced me to Elixir. Seems like eventsourcing and Elixir are a match made in heaven.
Erlang has its own runtime. Basically it spawns a scheduler per core and each scheduler is a thread. Then, OS-wise, each scheduler is a an OS thread. Within each scheduler you can start Erlang processes, which, OS-wise are "green threads" or "fibers". Erlang, however, it runs these fibers in isolation, that's why they're called "processes". I hope this brief explanation helps!
I came for copper and i found gold
So this is actually an incredibly interesting interview, I recommend actually taking the time to listen to this one.
Agreed, very enjoyable!
great talk. thanks guys.
That comment on the code formatters in Haskell made me chuckle, I can't keep track of all the formatting tools either :)
Great discussion.
Now I know how to pronounce his name :)
Is azure functions comparable to those concurrent processes? Not sure how Microsoft runs this on their side, I always assumed it was based on kubernetes pods, they have max runtimes of 15 minutes and are instantiated by request. I'm a c# dev who mostly has worked in kubernetes environments where people thought in terms of "microservices" but someone at work introduced me to eventsourcing, cqrs, feature slicing and high cohesion services. Then it evolved into running each feature in its own process, and now he introduced me to Elixir.
Seems like eventsourcing and Elixir are a match made in heaven.
Oh yeah, I think Yurii Rashkovskii had some nice event sourcing libraries, perhaps for Elixir too.
I am curios if an Erlang process is the same as the OS process. If not, it could be that one Erlang process runs within one OS process?
Erlang has its own runtime. Basically it spawns a scheduler per core and each scheduler is a thread. Then, OS-wise, each scheduler is a an OS thread. Within each scheduler you can start Erlang processes, which, OS-wise are "green threads" or "fibers". Erlang, however, it runs these fibers in isolation, that's why they're called "processes". I hope this brief explanation helps!
@@jonnmostovoy2406 it does
can you point me to the project you talk about at 38:00
github.com/cloudozer/ling This should be the one. :)
@@Serokell that's it