Hacker News new | ask | show | jobs
by djupblue 1547 days ago
So here's a challenge if anyone is up for it: Build a container orchestration engine that can run in 16MB of RAM on top of a Linux kernel.

Must have:

- Some form of networking (duh)

- Distributed state

- Distributed message queue (simple)

- Distributed scheduler

- Logging

Out of scope:

- Authorization/Authentication/Encryption

- REST/JSON/SSL/Web

2 comments

Do you need all of that for a software run on a Raspberry Pi (as article suggests) or similar embedded devices? I think just one application binary should be enough.
Is there some reason all of those things could not exist in the same binary?
distributed state like memcached?

what is popular for lightweight distributed message queue?

what is popular for lightweight distributed scheduler? is cron.. "distributed"?