Erlang Solutions Blog

If the success of Cisco, Whatsapp, Discord and nine nines worth of uptime isn't enough... you can link to our stodgy Fortune 100 company using it successfully! https://www.erlang-solutions.com/blog/how-hca-healthcare-used-the-beam…

Yeah, so we followed the link toast0 shared to get started: https://www.erlang-solutions.com/blog/erlang-and-elixir-distribution-w… It took some work to piece together but wasn't too complicated in the end. It's internal code that I can't quickly sanitize or I'd just dump it in a gist :/ Someone on the Elixir Forum might have a template or library handy though.

With insightful comment from leading industry voices - if you're working in FinTech or just curious about how this important industry will look as we recover from the last year, check out our in-depth FinTech Trends in 2021 Report > https://www.erlang-solutions.com/landings/fintech-trends-whitepaper/

BEAM based languages lack "good" debuggers, because they historically depend on tracing instead of debuggers. I recently wrote a blogpost about the tracing landscape in Elixir. https://www.erlang-solutions.com/blog/a-guide-to-tracing-in-elixir.htm… But the main reason is that BEAM languages are mainly used for concurrent computing which is a very difficult problem to debug with classical debuggers. I know it is not a mainstream way to "debug" but a very useful one once one learns it.

We have the XMPP Compliance Suites 2018[0] providing an overview of protocol-level specifications that a modern client or server should implement, and there was recently a nice article[1] for some example use cases. What is still missing is everything above the wire protocol level. The XSF, being the XMPP Standards Foundation, is guarding the protocols, and things like UX and client interoperability are considered as off-scope. However, there are people interested in these topics as well looking for fresh collaborators. [0] https://xmpp.org/extensions/xep-0387.html [1] https://www.erlang-solutions.com/blog/21-xmpp-use-cases-and-the-best-w…

One cannot not say something is "so open that..." ;-) But indeed, XMPP is open, very open. And indeed the major clients usually rely on the old era's ways of thinking messaging... They a far from contemporary, not only talking of features, but also the UX (User eXperience) and the general philosophy. I would recommend the reading of XEP-0387: XMPP Compliance Suites 2017 (and its successors): https://xmpp.org/extensions/xep-0387.html But I insist, this one is quite good, honestly: https://www.erlang-solutions.com/blog/21-xmpp-use-cases-and-the-best-w…

Hi, I'm quite new to the community myself, so I don't have any established contacts to share at the moment. I recommend checking here: http://www.meetup.com/Elixir-Berlin/ This company also has an office in Berlin now: https://www.erlang-solutions.com/contact.html

Non-Redirect Link: https://www.erlang-solutions.com/blog/mongooseim-1-6-riak-devops-love-… The original got captured by my filters. I have some huge MongooseIM Nodes in production, unfortunatly RIAK is not an Option for us.

To bring it back to a normal Erlang analogy level, the rooms are instances of Erlang VMs. Since Erlang has isolated memory between processes, the only way to ask one process in one virtual machine (reaching it either by its registered name or if you know the pid somehow) for data (i.e. values of variables) is to send messages to it. You can't access variables/data across VMs/processes directly, you have to talk to them. Regarding Erlang on Wheezy, I'd recommend the Erlang Solutions repository with pre-built and tested packages: https://www.erlang-solutions.com/downloads/download-erlang-otp

Here is the list of things that I feel are still holding Elixir back from wider adoption: 1. Not enough companies sharing their experience - most companies want to lead and not follow. There has been a lot of success with Elixir but too often I've heard companies not wanting to indicate they're using Elixir out of concern that it will tip off their competition (I've heard this from two companies now, big ones) or they just don't have a culture of sharing. The most impactful case study on Elixir was one of the first, the Bleacher Report case study https://www.erlang-solutions.com/case-studies/bleacher-report-case-stu… They did an excellent job of articulating the direct business value of transitioning from Rails to Phoenix. We need more of these stories shared 2. Lack of talent - this is a chicken or egg problem but one thing that comes up quite often. If there were more companies actively hiring in Elixir there would be more devs learning Elixir but companies are reluctant to hire for Elixir because there aren't enough devs. Most of the courses/guides are aimed at transitioning Senior level talent. At DockYard through our Academy https://academy.dockyard.com/ we decided to tackle this from the opposite end and commit to producing high quality junior Elixir engineers. 3. Higher price point for talent - the recent Stack Overflow surveys regularly rank Elixir at the top for cost. Personally I think this stat is being influenced by the fact that Elixir has a higher % of…

Highlights (emphasis mine): > Open source maintainers can request a free license by emailing [email protected] and including a link to their [GitHub] repository. Once approved, we provide a SAFE license for one month or up to a year, depending on the project’s needs, at no cost. The legalese[1] (is incoherent but apparently) does not pass the Curl test, that is, the maintainer of Curl—who gets money by providing commercial support for his completely FOSS project—wouldn’t be allowed to use this had it applied to him: > You can only use SAFE for open-source software. Any commercial use is prohibited. [1] https://www.erlang-solutions.com/policies/safe-for-open-source-project…

I understand it’s poorly promoted by the biggest users. But more of the web and world infrastructure runs on it than you realise. Here’s an old post with some examples - https://www.erlang-solutions.com/blog/which-companies-are-using-erlang…

Can you articulate the kinds of business problems Erlang is particularly well-suited to solve? When you choose Erlang for a project, what kind of return on investment do you think it typically offers? Does it lead to significant cost savings or help generate more revenue in ways that other languages might not? In situations where Erlang is chosen, what are some concrete examples of how it has demonstrably increased efficiency, reduced errors, or enabled new business opportunities that wouldn't have been as feasible with other technologies? Edit: I guess if I'd done any research myself before asking, I might've found this: https://www.erlang-solutions.com/blog/which-companies-are-using-erlang…

BEAM is the VM that Erlang, which Elixir (which this project uses) runs on: - https://www.erlang-solutions.com/blog/erlangs-virtual-machine-the-beam… - https://www.erlang.org/blog/a-brief-beam-primer/

Came to query the same thing. The product of this is targetted at custom enterprise solutions. Mentions specific platforms needed to meet government requirements etc. Maybe custom apps/platforms for interacting with support teams? Interfacing with custom hardware or systems to get updates passed around etc? I'm guess it's other things that are not for the "Slack"/Jabber use-case we might think of. https://www.erlang-solutions.com/technologies/mongooseim/

> Static typing is super critical for large projects YMMV very large project have been written in Erlang/Elixir without static typing and they've been wildly successfull i.e WhatsApp (based on Ejabberd), Ericsson network switches, RabbitMQ, CouchDB and a lot more, you can read about some of them here https://www.erlang-solutions.com/blog/which-companies-are-using-erlang… as a less knows example, an entire insurance company in my country with > 1 million customers

It probably helps that WhatsApp's backend is written in Erlang, which excels in fault-tolerance and reliability. https://www.erlang-solutions.com/blog/20-years-of-open-source-erlang-o…

I didn't write this blog, but it looks like it's got the right info: https://www.erlang-solutions.com/blog/erlang-and-elixir-distribution-w… You can skip to "Let’s use something else" if you've already got a good grasp of the knobs to tune with epmd.

Erlang's green threads are considered lightweight processes. They only communicate through message passing. When selling Erlang, don't focus on "telecommunications industry" but sell based on Whatsapp: http://highscalability.com/blog/2022/1/3/designing-whatsapp.html More: https://www.erlang-solutions.com/blog/which-companies-are-using-erlang…

> Again, a lot of guessing and assumptions what could be in a perfect XMPP world, but nobody finds nowadays. The German police and British health service would say that their XMPP implementations are pretty secure implementations: - https://twitter.com/inputmice/status/1203611711967813633 - https://hellopando.com/ / https://www.erlang-solutions.com/case-studies/pando-health-case-study/

Hewitt argues that erlang/elixir/beam isn't the actor model because of how Erlang processes receive/process messages more here: https://www.erlang-solutions.com/blog/lets-talkconcurrency-panel-discu… and here: https://codesync.global/media/almost-actors-comparing-pony-language-to…

Interesting. Here is also a podcast about the topic: https://thinkingelixir.com/podcast-episodes/017-jit-compiler-for-beam-… Had a brief look at asmjit; as it seems it only supports x86 and x86_64 and is not really an abstraction (i.e. a platform independent IR). I will try to find out why they didn't use e.g. LLVM or sljit. EDIT: according to this article (https://www.erlang-solutions.com/blog/performance-testing-the-jit-comp… the speed-up factor caused by the JIT is about 1.3 to 2.3 (as a comparison the speed-up between the PUC Lua 5.1 interpreter and LuaJIT 2.0 is about factor 15 in geometric mean over all benchmarks, see http://luajit.org/performance_x86.html).

That’s an “it depends” for me. I do always want the transcript, but let’s appreciate that a competent lecturer brings a topic to life. You don’t have to be Richard Feynman, but you do have to reveal and conceptualise at a pace an informed and inquisitive brain latches onto. Most video content is not at this level; it’s often either glibly oversimplified (content marketing), bogged down in minutiae (how-to guides), or buried under irrelevancies (what’s up guys). There is something I’d often prefer to consume as a AV recording, and that is interviews/panel discussion. The nuances of articulation, even body language may be informative. Compare and contrast the transcript with the video at https://www.erlang-solutions.com/blog/let-s-talkconcurrency-panel-disc… for example.

WombatOAM seems similar: https://www.erlang-solutions.com/products/wombatoam.html

why wouldn't you just use rabbit rpms that depend on the exact correct versions of erlang? aka els-erlang https://www.erlang-solutions.com/resources/download.html Linux distros have always been terrible places to find reliable packages.

1. See: https://blog.stenmans.org/theBeamBook/#_the_tagging_scheme (search for "64 bytes") and code: https://github.com/erlang/otp/blob/OTP-22.0.7/erts/emulator/beam/erl_b… 2. See: https://www.erlang-solutions.com/blog/erlang-garbage-collector.html There's no thread-local GC, it's really per process. For instance a scheduler thread that's running a process and hits the need to do an expensive GC may delegate the task to a dirty scheduler (another type of thread, dedicated to long blocking tasks), and go back to running other processes in the meanwhile. It's frequent for processes to move around between schedulers, they steal work from each other.

not exactly, but you can have a look at how GC works in BEAM[1][2]. [1]: https://www.erlang-solutions.com/blog/erlang-19-0-garbage-collector.ht… [2]: https://hamidreza-s.github.io/erlang%20garbage%20collection%20memory%2…

Erlang has a per-process GC - each Erlang process has it's own heap and it's own garbage collector. There's no VM-wide GC. This usually means the GC pauses apply only to a small part of your system, while the other parts are running completely normally. There's a good article that describes it in depth: https://www.erlang-solutions.com/blog/erlang-19-0-garbage-collector.ht…

I don't know how the Erlang GC works so I can't really comment on that If you're interested, here are a few helpful blogposts on the subject: - This is a pretty short and readable post, though it's a bit old (2008): "Garbage Collection in Erlang" [0] - A more detailed (and recent -- 2015) blogpost: "Erlang Garbage Collection Details and Why It Matters" [1]. - And this is the most up-to-date description, from April 2016 concerning Erlang R19, by Lukas Larsson, who works on the Erlang VM -- it is long, but well-written and has nice illustrations [2]. [0] http://prog21.dadgum.com/16.html [1] https://hamidreza-s.github.io/erlang%20garbage%20collection%20memory%2… [2] https://www.erlang-solutions.com/blog/erlang-19-0-garbage-collector.ht…

Redirect through external tracker (go.pardot) blocked by ublock; actual article: https://www.erlang-solutions.com/blog/how-to-analyse-a-beam-core-dump.…