Fork me on GitHub
#yada
<
2016-03-28
>
gtrak17:03:14

I'm really looking forward to trying yada for a new project, I'm confused by a simple thing, if the goal of yada is to return a ring handler, why is it coupled to aleph? Can someone really drop yada into an existing ring/jetty app?

gtrak18:03:10

Also, am I correct in that libs+aleph is a lighter-weight runtime than say jetty+pedestal? That's an assumption that makes yada attractive for a microservice, with more out of the box than say http-kit.

dominicm18:03:52

@gtrak: The coupling to aleph is due to yada's async handling. The ring interface doesn't have native support for async, so you have to couple it to the web server implementation.

nha22:03:38

@gtrak: As far as I know, yada is not tied by nature to Aleph, it just happens to be the first server supported, and the only one which allows to return manifold handlers. Having used both yada and pedestal yada feels much more lightweight (ex. reloads much faster in my component system).