Hi Peter, couldn’t find this in the docs and I guess many others will be wondering the same, so a few questions for you:

• How does this differ from Phoenix?
• When would you recommend people use this instead of Phoenix?
• Can this be used in multiple layers of an Elixir app, like Phoenix can?
• What does it have that Phoenix doesn’t?
• What doesn’t it have that Phoenix does?
• How does performance compare to Phoenix?
• Have you got any URLs of sites using this in production?

I think in any case it’s worthwhile to spend ~30 min watching ElixirDaze 2018 - Purify your web development.

• Raxx is a different abstraction than Plug. Phoenix is built around Plug. From what I’ve seen the Raxx abstraction aligns more closely with the HTTP protocol.
• Ace is used instead of Cowboy.

From a full stack perspective someone gravitating in front end matters to Vue.js in the “Vue.js vs React” discussion would likely gravitate towards Phoenix - until the Plug abstraction gets in the way.

Raxx seems more for control enthusiasts who don’t mind assembling their own framework in order to have “not a shred of bloat” in their system and prefer an abstraction more closely aligned with HTTP.

I especially liked how the streaming upload looked like a short-lived process handler.

Fix default ports for tutorial in 0.5.2

Building a distributed chatroom with Raxx.Kit tutorial did not work due to bug with default ports. This latest release fixes that.

0.12.1 released

• Small fix for a bug introduced with Elixir 1.9 where Mix task raxx.new would fail in all cases due to a changed return value for Mix.Generator.create_directory.

0.9.0 Overhaul of middleware and project structure

From Changelog

• Use Raxx.Stack for runtime middleware.
• Move assets and public files into www directory.
• Clean up child_spec functions for each service.
• Namespace all action modules under Actions module.
• Create a separate WWW.Router module.
• Add an example integration test using :httpc