<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Phoenix-Framework on Scholion</title><link>https://scholion.thluiz.com/tags/phoenix-framework/</link><description>Recent content in Phoenix-Framework on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Thu, 22 Oct 2026 02:56:08 +0100</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/phoenix-framework/index.xml" rel="self" type="application/rss+xml"/><item><title>Things Elixir's Phoenix Framework Does Right</title><link>https://scholion.thluiz.com/notes/things-elixirs-phoenix-framework-does-right/</link><pubDate>Mon, 05 Oct 2020 08:42:59 -0300</pubDate><guid>https://scholion.thluiz.com/notes/things-elixirs-phoenix-framework-does-right/</guid><description>The article argues that Phoenix sits near the middle between flexible and strict frameworks, stands out in persistent communication, benefits from BEAM-based concurrency, and handles failures and clusters with built-in supervision.</description></item><item><title>Why did we choose Elixir for the backend development of MoodleNet?</title><link>https://scholion.thluiz.com/notes/why-we-chose-elixir-for-moodlenet-backend/</link><pubDate>Mon, 07 Sep 2020 16:48:24 -0300</pubDate><guid>https://scholion.thluiz.com/notes/why-we-chose-elixir-for-moodlenet-backend/</guid><description>The post says MoodleNet chose Elixir and Phoenix for backend development because of performance, scalability, concurrency, reliability, simplicity, flexibility, correctness, and developer productivity.</description></item></channel></rss>