ElixirWeekly

Every Thursday: No frills, no click-through, no spam.

Here's what the latest issue looks like:

Issue #354

This week in Elixir

Monolith vs Microservices: With Elixir You Don't Need to Choose
In this blog post, Dmitry is chiming in on the microservices vs monolith debate that heated up again.

How Elixir Solves a Difficult Security Problem
Thread safety issues lead to complex and high severity security bugs. Michael shows how Elixir’s approach to concurrency eliminates this problem.

Building a Drag-and-Drop List with LiveView and SortableJS
Add drag-and-drop functionality to your Phoenix LiveView app with SortableJS and LiveView Hooks!

Upload Encrypted Files to S3
Peter explains how to encrypt, decrypt, upload, and download files from S3 and how to display them in LiveView.

Experimenting with Elixir Metaprogramming: Agentize
Rodrigo wrote a simple macro that when used within a module with a struct generates a sub module that is an Agent for keeping a map of those structs.

Even more from around the Elixir community

The Changelog: Livebook’s Big Launch Week w/ José Valim Podcast

Elixir Wizards: Saša Jurić on The Future of Training & Education in Elixir Podcast

Elixir Outlaws: Tech Talking Green (and Yellow) Podcast

Thinking Elixir News Podcast

How to Check If Two Lists Contain Overlapping Elements Video

Pacman Rules in Elixir Blog post

Empty Values and Ecto Changesets Blog post

Deploying After mix ecto.dump Blog post

Elixir Code Coverage with Partition Test Blog post

Introducing NervesHub 2.0 Project update

Submit your blog post/project update

That's it for this round, have a great day!
@rrrene from ElixirWeekly

If you like this newsletter, please tell the world!

You can view this issue in your web browser.

You can subscribe below:

Questions & Answers

Can I submit things I made to be included in the next issue?

Yes! Simply post them to ElixirStatus and you can be sure that they land on my radar.

Is my email address safe with you?

Yes. I'd like to consider myself a trustworthy individual, but then who doesn't?

I am, however, an active member of the open-source Elixir community and the maintainer of Credo and ElixirStatus. I will NOT ruin my reputation by selling your data to a third party.

Why do you require me to confirm my email address?

I just believe that requiring double opt-in to subscribe to any email-based system is a win for both parties: You are safe from unintentionally subscribing and I can be confident that you actually own the email address and want to receive the newsletter I send you :)

Contact

Feedback? Questions? Anything else?

Please contact René Föhring (email or tweet @rrrene for a quick conversation).

ElixirWeekly by @elixirstatus

ElixirWeekly

Questions & Answers

Contact