7 ms·
Have you looked at https://habitat.sh https://habitat.sh ?
by echohack5 8y ago
Have you looked at https://habitat.sh https://habitat.sh ?
- omn1 8y agoI actually did and I love the idea! In my opinion, that's gonna be the next wave of container management solutions. If you think about it, you shouldn't care about container orchestration at all; you should care about services. Habitat ships the orchestrator together with every service. That sounds strange and redundant at first, but if you think about it, it has some nice advantages: * Services are fully self-contained and can run anywhere (in dev, stage, prod) without any changes. * By tagging services, one can create a service-mesh quite easily without having to think about network-topologies. Services find each other automatically (I think via a Raft/Gossip protocol). I haven't looked at it too closely yet, but it's on my list. Fair disclaimer: I know the folks behind it from the Rust community.
- mr_tristan 8y agoI took a look at it, and if you were starting from scratch, I'd give it a serious look. The main reason I didn't push for it were mostly internal politics - we'd have to setup an on-premise installation of the Habitat Builder. And we have rather (ridiculous) requirements that would have made that a massive hurdle. Habitat is very new, so I'd expect to spend some time nailing down exactly what you want for your stuff. But, it's very easy to use.