Issue #19: CRDTs, NoSQL Injection in Phoenix and IntelliJ Elixir v4.6.0

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

Here's what the latest issue looks like:

This week in Elixir

Readings in conflict-free replicated data types (CRDTs)
Christopher put together a reading list regarding the topic of conflict-free replicated data types (CRDTs, the ones Phoenix Presence is based on).

NoSQL Injection in Phoenix Applications
Are you using MongoDB in your Elixir/Phoenix projects? Watch out for NoSQL injection vulnerabilities!

Build Your Own Real-Time Web Service with Elixir/Phoenix
These are the slides for the talk "Build your own real-time web service with Elixir/Phoenix" at Manchester Lambda Lounge.

An Elixir package which converts ids to proquints, Identifiers that are Readable, Spellable, and Pronounceable.

IntelliJ Elixir v4.6.0 released
This new version of IntelliJ Elixir now includes Completion and Go to Declaration for functions and macros.

Vim for Elixir
Bodo shared his current vim configuration to edit Elixir code.

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 :)


Feedback? Questions? Anything else?

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