or subscribe with
Join 3,000+ readers for one email each week.
Digests » 316
Join the Functional Works community to discover the world's most innovative tech companies that use Functional Programming, read community content, find jobs and discover the latest market trends. Create an account to get access to a personalized dashboard with recommended jobs and reading resources.
this week's favorite
One of the features that fascinate me most about Elixir is pattern matching. I always wonder if there is a way to solve what I need using it and I love exploring it. When you combine the beauty of pattern matching with the power of immutability some things almost seem magical but they are not! It is not my focus to cover everything about pattern matching and immutability but instead to demonstrate how we can use pattern matching instead of guard clauses to implement clean control flows in Elixir.
Phoenix LiveView provides you all of the tools you need to build interactive, real-time applications with Elixir, while keeping your brain firmly rooted on the server-side. LiveView applications are lightning fast, in part because LiveView is specifically designed to minimize the amount of data sent between the client and the server.
Previously we looked at different ways we can kill (or attempt to kill) a process and what happens in each case. Now let’s see what happens when a linked process dies. The tl;dr is in the table below.
When writing API with Phoenix and render json to client, for some fields I want to keep it original value. For some fields, I want to do some calculation or format data before returning. And I want to render Ecto association too.
In this article, I will describe the roles and implementation of aggregates in Elixir and PostgreSQL.
Ever wondered how a payment platform in Elixir & OTP would look like? Want to build one? Join us!