Replies: 4 comments 1 reply
-
thanks @gedw99 -- that looks really neat! What would you use it for? |
Beta Was this translation helpful? Give feedback.
-
Ah good question At the moment I use siot with some other things. Caddy These things need to also run along side siot. Supervision trees are great for this. I also am exploring siot node workers being wasm . Wam with Wazero runs fine on iot. There is no cgo. So I can also run the node workers as wasm inside a supervision tree ! You could run all this without supervision trees ! It’s just standard golang code of course but perhaps one could fail. Also the trees aspect seems to be nicely aligned with nodes being dependent on other nodes . So you can tear down a node and all its child nodes get teared down too. the reason I am using caddy, minio and git is for deployment. You can then develop a node worker in a git repo and got release it . The caddy server can host it and the git can pull and compile it to wasm . Minio can hold the wasm. This gives siot a more complete development and deployment architecture so by using supervision trees I can include all this is a siot system have have robust failure management and nodes inside nodes with decent “ garbage collection “. |
Beta Was this translation helpful? Give feedback.
-
Interesting ideas -- I've been pondering a dynamic plug-in architecture for SIOT, and WASM may be the solution for some cases. However, I'm still a ways away from this becoming a priority for my projects as there are still tons of other things that need to be implemented. Currently, my deployment model is to simply deploy SIOT. |
Beta Was this translation helpful? Give feedback.
-
We don't want just anyone's code running on our hardware. Keep pushing the limits, you guys! I can't wait to see what you come up with. |
Beta Was this translation helpful? Give feedback.
-
https://github.com/ergo-services/ergo
Beta Was this translation helpful? Give feedback.
All reactions