Digests » 173
Alchemists never share their recipes. But we do. Subscribe to our Elixir Alchemy email series and learn the tricks that make your Elixir even better. Poof!
this week's favorite
Elixir is known for being a language made for building distributed applications that scale, are massively concurrent, and have self-healing properties. All of these adjectives paint Elixir in a grandiose light. And for good reasons!
If you work with Elixir on web services, you may have come across a library I work on named Cachex. Although the name makes it somewhat obvious, this is a library based on caching expensive data in memory. It works inside your application layers using the Erlang Term Storage (ETS) under the hood, whilst offering a bunch of convenience layers above.
Since I like playing with new stuff, I set up a Phoenix 1.4 project capable of building Elm code. Given I bumped into several quirks, I decided to write a simple step-by-step guide detailing the process, and a couple tricks you might find handy.
Through its roots in Erlang, Elixir’s robustness and reliability are often mentioned as its greatest advantages. The ultimate example of this being its ability to upgrade an application without having to restart it.
Maps are used extensively in Elixir. Updating nested maps in Elixir is straightforward if you already know the structure of your map beforehand (in this case, you may want to use a Struct instead).