cowboy VS heroku-buildpack-elixir

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.

But not all hope is lost, we have the ability to use custom buildpacks to support it ourselves. And there is one already available that Akash Manohar and his contributors built for us.