What is Nebulex?

Overview of Nebulex, an Elixir open source cashing library
17 August 2017   1009

Caching is one of the mos popular methods to improve performance. There are different cashing options in Elixir available. But most of them are focused on local caching. Most of the cases developers deal with distributed systems, which involves at least two nodes, therefore, sometimes a local cache might be not enough. So, there should be a a tool or library that give the ability to create different caching topologies depending on our needs; it could be a simple local cache, a distributed or partitioned cache, or even a near cache topology. Nebulex can help you with it.

Nebulex is an open source caching library written in Elixir, with Ecto influence. Nebulex features:

  • Simple and fluent API inspired by Ecto
  • Flexible and pluggable architecture like Ecto – based on adapter pattern
  • Built-in cache adapters
    • Local generational Cache
    • Distributed or Partitioned Cache
    • Multi-level Cache
  • Support for different cache topologies – Partitioned, Near, etc.
  • Time-based expiration
  • Pre/post execution hooks
  • Transactions (key-locking)
  • Key versioning – optimistic offline locks
  • Optional statistics gathering

Additionally, Nebulex has good documentation, starting guide, and available examples. Developers ask to create an issue if any bugs appear.

Elixir v1.7.0-rc.0 Released

Development team ask community to try out new release 
17 July 2018   195

Elixir team rolled out zero release candidate for version 1.7.0.

Hi everyone,

We have just released v1.7.0-rc.0.

Please give it a try! You can either compile the v1.7 branch from source OR use the precompiled files, as described in our install page 11.

Note that you will need {:ex_doc, "~> 0.19-rc"}if you want to generate docs using the release candidate.

Happy coding!
 

josevalim

Creator, Elixir

Currently Elixir supports two metadata keys: :deprecated and :since. Other keys will be added in the future. 

To access the new documentation, developers should use Code.fetch_docs/1. The old documentation format is no longer available and the old Code.get_docs/1 function will return nil accordingly.

Tools like IEx and ExDoc have been updated to leverage the new format and show relevant metadata to users

Learn more at GitHub