Why we chose Elixir

1. Phoenix

   1 126 22,159 9.7 Elixir

   Peace of mind from prototype to production

   

   After some time debating which technologies we should use, we decided to go with Elixir and Phoenix. In short, these tools gave us the productivity, stability, safety, and scalability (the company was planning on opening up the application to the public, with a new API added to the mix, so future performance was a bit of a concern) that seemed appropriate for the company's plans.

2. InfluxDB

   www.influxdata.com featured

   InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

   

3. Symfony

   2 176 30,395 10.0 PHP

   The Symfony PHP framework

   

   Some time ago, I worked with a team to rebuild a company's internal web application, which was based on a very outdated version of Symfony, and was no longer salvageable for several reasons.

4. Elixir

   3 159 25,333 9.9 Elixir

   Elixir is a dynamic, functional language for building scalable and maintainable applications

   

   After some time debating which technologies we should use, we decided to go with Elixir and Phoenix. In short, these tools gave us the productivity, stability, safety, and scalability (the company was planning on opening up the application to the public, with a new API added to the mix, so future performance was a bit of a concern) that seemed appropriate for the company's plans.

Suggest a related project