3 ms·
> We tried Deis briefly but ultimately decided that it was more complicated than we felt it needed to be. That kind of reminds me of https://xkcd.com/927/ http
by smanuel 11y ago
> We tried Deis briefly but ultimately decided that it was more complicated than we felt it needed to be.
That kind of reminds me of https://xkcd.com/927/ https://xkcd.com/927/
Sorry if that's not the case. I've also played briefly with Flynn and Deis and I haven't found anything that complicated that would need a whole rewrite and changing the entire approach. Moreover with Deis I can easily change providers (DO, AWS, Azure, etc.) and with Emprire I'm bound to ECS. At least that was my first impression, I have to read more.
- athrun 11y agoIMHO, it's best to see Empire/Deis/Dokku/etc. as a mean to an end, not the end itself. While Empire itself may be tied to AWS, your app is still a portable, 12-factor, Heroku-compatible app. You can run it elsewhere.
- ejholmes 11y agoOur approach was to re-use as much existing technology as possible, which is not the case for most others. That's the "complication" I'm referring to here. Empire grew from the need for a production grade platform that was going to be stable. Empire doesn't actually lock you into ECS. The scheduling backend is pluggable and could support Kubernetes/Swarm in the future.