home
industries
releases
$designs
hoff.kitchen
metapages
A low-latency, asynchronous distributed cloud ecosystem, smart-home engine and personal assistant.
"I'm doing a (free) cloud middleware system (just a hobby, won't be big and professional like kafka) for hoff.industries." - hoff
A cloud ecosystem, smart home engine and personal assistant, written in low-level languages. Self-deployed; doesn't phone home with a simple and tweakable communication protocol. Infinite service scalability is the goal here.
The MVP for M.A.R-T>Y. v1.0 will not be anything too crazy. In fact, it will likely be completely unoptimal. That's the benefit of iterative design. The short-term goal is to write SOMETHING using MMP v1.0 and figure out optimisations from there.
The MVP implementation of a M.A.R-T>Y. ecosystem would entail:
Going to start on this in April 2023.
The idea is to take the UNIX philosophy and add network capability. You would write your daemon, as if it were to run on a standard UNIX system; do one thing, and do it well. That daemon now also has the ability to IPC across a network. That's M.A.R-T>Y. - it naturally shapes into a microservice architecture.
One of the systems in your computer network should be designated as a control server. This system would host a remote file system with offline sync capabilities, a service intercommunication server and other various M.A.R-T>Y. compatible daemons.
A 24/7 server connection is not required; most client-based M.A.R-T>Y. daemons are able to detect if they cannot connect to a server and will perform their tasks as best they can until that connection is restored.