Elixir’s Platform as a Service

Distributed clustering is one of the coolest parts of Elixir. You can have distributed Phoenix channels without Redis. You can have global cron jobs without a separate scheduler. You can design your app the way you want to and keep one global process per game or chat room. You can distribute work load evenly across machines. The use cases are endless.

Remote Console let’s you debug your node and run one-off tasks.

Remote Observer gives you a GUI to monitor and inspect your node.

Phoenix can handle over two million simultaneous websocket connections on a single node and it’s great for massively real-time apps. Limits on your connection counts and duration will hold you back.

GenServer state, ETS, cachex, etc make it possible to create ridiculously high performance, fault-tolerant apps but daily restarts will get in your way.

Full SSH access lets you do whatever you want. Enough said.

In Ruby on Rails, it’s common to use Redis, Sidekiq, and dedicated worker processes to run background jobs. With Elixir’s distributed async Tasks, you might not need any of those.

Distributed Phoenix channels don’t need Redis if you have your nodes clustered.

With ETS, DETS, Mnesia, cachex, etc, you really don’t need Redis or Memcached anymore.

Migrations run as Elixir processes, you don’t need to run an entirely new instance.

With Quantum, cron jobs run as Elixir processes, no need to pay for a dedicated instance just to run a cron job.

With Elixir you can connect a Remote Console directly to your node instead of spinning up a new instance that isn’t even serving traffic.

With Remote Observer, you get tons of free, built-in stats, monitoring, and tools.

We use Let’s Encrypt to provision and manage your TLS certificates automatically and completely free.