jorgeavaldez

I can't help but second this. It's a total joy to use and lets me focus on doing what I need to do without constant lag and yak-shaving configuration files.

They do sound very sci-fi. I would say it made me more or less inclined to dig a little deeper myself hahahaha.

Genservers are an abstraction encapsulating the typical request/response lifecycle of what we would consider a "server", but applied to a BEAM-specific process. Like "general server".

Oban allows for job processing, instrumented much like you would any other process in the BEAM. This is an external library while genserver is built in.

No, typically you register a node and instruct it on what processes to run. But there are libraries to help instrument this kind of behavior.

For elixir:

- https://github.com/derekkraan/horde

- https://github.com/bitwalker/swarm

For some people (myself included) the technology is part of the fun. The cargo cult popularity can definitely influence the decision to play with the technology, and by no means does it indicate that it is entirely appropriate for the task at hand. I personally use it as an exercise to familiarize myself with the patterns in a toy environment, which leaves me better equipped to apply them for a problem that lends itself to the technology. It also helps in preparing me to find those applications with a better understanding of the costs and semantics. While the knowledge may not be used for a practical purpose, at the end of the day, I learn something new, and I have a new way of looking at problems and understanding how to solve them with fresh perspective.

I would definitely recommend setting something up with https://www.notion.so/