thoas VS cowboy

One of the ideas we had with Nova was that it should be easy to configure it or add a module or libraries that you want to use. Example are that if you don't specify a json package Nova will use Thoas. But if you configure that you would like to use jsx for example it will use that so long you add it as a dependency in your application.

According to the 'Server' response header, Cowboy is the customer facing web server https://github.com/ninenines/cowboy

===> sh(git clone -n https://github.com/ninenines/cowboy .tmp_dir636214859401) failed with return code 128 and the following output: Cloning into '.tmp_dir636214859401'... fatal: unable to access 'https://github.com/ninenines/cowboy/': SSL certificate problem: unable to get local issuer certificate

RE: HTTP/Web Sockets/TCP/UDP/etc. - check out NineNines libraries: Ranch (TCP Socket Acceptor), Cowboy (HTTP Server), Gun (HTTP client), and CowLib (General HTTP/SPDY library) are pretty good from what I hear.

Ranch is a pretty well optimized and battle hardened tcp acceptor. It powers the Cowboy/Phoenix server which scales to extreme level of concurrency and low latency. Cowboy uses ranch to pool and accept connections and I believe it uses {active,once}.

https://github.com/ninenines/cowboy

https://github.com/ninenines/ranch

I have a web application which uses cowboy and cachex every so often cachex errors, which means my server returns a 500.

Cowboy is a small, fast and modern HTTP server for Erlang/OTP.

plug_cowboy: Uma implementação do Cowboy para o Elixir.

We are going to be using the light http server Cowboy and the adapter Plug to return our data.

At the core of your web app (and any other app that works with HTTP) will be Cowboy, but further than that, you need to know what a web app consists of and pick your tools for each layer separately.