hive VS grav

That would indeed be super useful to extend self hosted automation tools like Huginn. From what I understand, wasm/wasi modules don't have full networking or filesystem access support yet. So you probably have to rely on specific runtimes to provide hooks for doing that, and regular code won't work out of the box.

1. https://github.com/suborbital/reactr

In the end, a combination of those factors led me to build the three main components of Atmo rather than use something off the shelf. Choosing to build the web server framework caused me to build Vektor. The need for a highly custom scheduler caused me to build Hive. The need for a dependency-free and decentralized message bus with tight integration with Hive caused me to build Grav. Some people may call this yak shaving, but I believe it was fundamental to building Atmo.

Since all of this behaviour is provided by the SUFA framework, developers still need only concern themselves with writing the functions and defining how to compose them. Developers can even run a single instance in their local development environment, and then production environments can run in capability groups. Atmo runs functions compiled to WebAssembly modules and uses the Grav messaging mesh to provide meshing functionality, which provides the flexibility and simplicity needed to build powerful applications that are never complicated.