Chicago Boss is a heavy framework, so don't hesitate to start with Cowboy and add the remaining pieces as you need them. It goes without saying that something l

Chicago Boss is a heavy framework, so don't hesitate to start with Cowboy and add the remaining pieces as you need them. It goes without saying that something like CB is complex and that it can make simple tasks like building an OTP release more challenging. See for instance that `init.sh' uses Rebar[1] internally rather than a standard `erl -s MOD FUN ...` invocation. In general the philosophy seems to be to hide many OTP things from the end-user, for better or worse (given how powerful OTP is, I would say this is worse for the individual versed in OTP but better for the one coming from Rails or something like that, who doesn't want to have to scale the steep learning curve. That developer is Chicago Boss' target audience[2]). It is very much a monolithic distribution akin to Django. [1] https://github.com/evanmiller/ChicagoBoss/blob/master/skel/init.sh https://github.com/evanmiller/ChicagoBoss/blob/master/skel/i... [2] https://github.com/evanmiller/ChicagoBoss#philosophy-and-features https://github.com/evanmiller/ChicagoBoss#philosophy-and-fea...