ra
burrito
ra | burrito | |
---|---|---|
7 | 11 | |
778 | 818 | |
0.5% | 1.5% | |
8.9 | 8.1 | |
5 days ago | 19 days ago | |
Erlang | C | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ra
-
The Erlang Runtime System
Erlang/OTP doesn't handle leader election, and by itself is bad at handling netsplits.
There is https://github.com/rabbitmq/ra which is a Raft implementation in Erlang that is Jepsen-tested. You could use it to build "etcd in Erlang", or https://github.com/rabbitmq/khepri which is built on top of Ra.
-
Ask HN: Good examples of fault-tolerant Erlang code?
Just to add to this, there are some implementations of things like consensus algorithms in Erlang such as Ra: https://github.com/rabbitmq/ra
- Elixir at Ramp
-
An Animated Introduction to Elixir
You may find these interesting...
- "The Onion Layer Theory" https://learnyousomeerlang.com/building-applications-with-ot...
- "On Erlang, State and Crashes" http://jlouisramblings.blogspot.com/2010/11/on-erlang-state-...
- "Why Restarting Works" https://ferd.ca/the-zen-of-erlang.html (search for "Heisenbug")
> you should store the state in the external system
Disk works too, but if you're multi-node this means you now have a distributed database embedded in your system, which may or may not be your goal :)
RabbitMQ does this, they developed a library for "persistent, fault-tolerant and replicated state machines" based on Raft: https://github.com/rabbitmq/ra.
- Question about a Decentralized Timeline
-
Building Aggregates in Elixir and PostgreSQL
Here is link number 1 - Previous text "Ra"
burrito
- Why are Apple Silicon VMs so different?
- Show HN: Burrito v1.0.0 – Wrap Elixir Apps into Standalone Binaries
-
Elixir at Ramp
Most of the BEAM isn't well-suited for trends in today's immutable architecture world (Docker deploys on something like Kubernetes or ECS). Bootup time on the VM can be long compared to running a Go or OCaml binary, or some Python applications (I find larger Python apps tend to spend a ton of time loading modules). Compile times aren't as fast as Go, so if a fresh deploy requires downloading modules and compile-from-scratch, that'll be longer than other stacks. Now, if you use stateful deploys and hot-code reloading, it's not so bad, but incorporating that involves a bit more risk and specific expertise that most companies don't want to roll into. Basically, the opposite of this article https://ferd.ca/a-pipeline-made-of-airbags.html
Macros are neat but they can really mess up your compile times, and they don't compose well (e.g. ExConstructor and typed_struct and Ecto Schemas all operate on Elixir Structs, but you can't use all three)
If your problem is CPU-bound, there are much better choices: C++, Rust, C. Python has a million libraries that use great FFI so you'll be fine using that too. Ditto memory-bound: there are better languages for this.
This is also not borne from direct experience, but: my understanding is the JVM has a lot more knobs to tune GC. The BEAM GC is IMO amazing, and did the right thing from the beginning to prevent stop-the-world pauses, but if you care about other metrics (good list in this article https://blog.plan99.net/modern-garbage-collection-911ef4f8bd...) you're probably better off with a JVM language.
While the BEAM is great at distribution, "distributed Erlang" (using the VM's features instead of what most companies do, and ad-hoc it with containers and infra) makes assumptions that you can't break, like default k-clustering (one node must be connected to all other nodes). This means you can distribute to some number of nodes, but it's hard to use Distributed Erlang for hundreds or thousands of nodes.
Deployment can be mixed, depending on what you want. BEAM Releases are nice but the lack some of the niceness of direct binaries. Libraries can work around this (like Burrito https://github.com/burrito-elixir/burrito).
If you like static types, Dialyzer is the worst of the "bolted-on" type checkers. mypy/pyright/pyre, Sorbet, Typescript are all way better, since Dialyzer only does "success typing," and gives way worse messages.
[1]: https://morepablo.com/2023/05/where-have-all-the-hackers-gone.html
-
Building Apps with Tauri and Elixir
The answer was given by the Elixir community with burrito which enables users to pack up everything an Elixir application needs within a binary namely Zig Archiver to package the binary and Zig Wrapper that wraps the Erlang Virtual Machine to be used in multiple platforms (Zig + Rust in the same project 🤯).
- Burrito: Cross-Platform Elixir Deployments
-
Is Elixir a good fit for a hobbyist? (Homelab automation/Content Backlog Management)
Might be worth looking into burrito for that use case?
-
Which language to choose ?
Elixir is extremely practical for building systems, I know some sysadmin/devops that write their tools in it - which is maybe a bit of a leap for most. It has better support for cli stuff these days but it's not it's strong suit - you can create single-bin packages with stuff like https://github.com/burrito-elixir/burrito or regular "mix releases". (LiveView is very sexy.) It's not statically typed. There is some experimental skunkworks project to add typing to it but probably wont see any public preview until mid/late next year as I understand it.
-
Sell me on Elixir
I would consider 1 to be the major blocker but Burrito has addressed many of the concerns here, including cross-compilation. The only downside of Burrito is that the first boot has to unpack the runtime (which is sub-second in my experience).
-
FireZone – Tailscale Alternative – The Open Source VPN Server and Firewall
Sure! Elixir's been great. Phoenix is a joy to work with, and many of the concurrency primitives built into OTP make it the perfect foundation for a product like this. And rustler makes it super easy to add low-level / native code.
I will say the big downside to using Elixir is that distributing releases is a bit cumbersome. `mix release` expects that you're building on the same OS / version as you'll be running on, though we're looking into using something like burrito [1] aim to alleviate this.
[1] https://github.com/burrito-elixir/burrito
-
Zig monthly, October 2021: Games, gamedev, Elixir, tools and more
I was intrigued so I went to hunt for the Burrito repo [1].
I thought it was some sort of Erlang native compiler written in Zig (which sounds like an incredible pain in the ass), but it's really "just" a cross-platform installer. Still useful !
[1]: https://github.com/burrito-elixir/burrito/issues?q=is%3Aissu...
What are some alternatives?
lasp - Prototype implementation of Lasp in Erlang.
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
MicroRaft - Feature-complete implementation of the Raft consensus algorithm in Java
ex_tauri - Utility to build Phoenix Desktop applications using web views from Tauri
khepri - Khepri is a tree-like replicated on-disk database library for Erlang and Elixir.
sendgrid-v3 - Haskell Sendgrid v3 API Library
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
Rustler - Safe Rust bridge for creating Erlang NIF functions
Atomix - A Kubernetes toolkit for building distributed applications using cloud native principles
babashka - Native, fast starting Clojure interpreter for scripting
buffstreams - A library to simplify writing applications using TCP sockets to stream protobuff messages
capacitor - Build cross-platform Native Progressive Web Apps for iOS, Android, and the Web ⚡️