# Erlang Erlang is a programming language used to build massively scalable soft real-time systems, with runtime support for concurrency, distribution, and fault tolerance. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## What Now? Handling Errors in Large Systems DevFeed: [What Now? Handling Errors in Large Systems]() Original publisher: [Read original article]() Author: Marc Brooker Published: 2025-11-20T00:00:00Z Content type: article Language: en Sources: [Marc Brooker's Blog](), [Marc Brooker's Blog]() Topics: [systems](), [Resilience](), [Rust](), [Processes](), [autoscaling](), [Amazon Web Services](), [Serverless](), [Erlang](), [Containers](), [servers]() Tags: [architecture](), [autoscaling](), [aws](), [component](), [errors](), [http](), [outage](), [process](), [resilience](), [rust](), [server](), [serverless](), [servers](), [systems]() ### AI overview An analysis of error handling in large systems, using Rust's Result and unwrap as a starting point. It argues that whether a component should crash is a system-wide architectural decision shaped by failure correlation, error-handling layers, business logic, and the value of continuing with a last-known-good configuration or data version. ### Source excerpt What Now? Handling Errors in Large Systems More options means more choices. Cloudflare's deep postmortem for their November 18 outage triggered a ton of online chatter about error handling, caused by a single line in the postmortem: .unwrap() If you're not familiar with Rust, you need to know about Result, a kind of struct that can contain either a successful result, or an error. unwrap says basically "return the successful results if there is one, otherwise crash the program"1. You can think of it like an assert. There's a ton of debate about whether asserts are good in production2, but most are missing the point. Quite simply, this isn't a question about a single program. It's not a local property. Whether asserts are appropriate for a given component is a global property of the system, and the way it handles data. Let's play a little error handling game. Click the ✅ if you think crashing the process or server is appropriate, and the ❌ if you don't. Then you'll see my vote and justification. One of ten web servers behind a load balancer encounters uncorrectable memory errors, and takes itself out of service. ✅ ❌ Your vote: My vote: ✅ Uncorrectable memory errors are independent, and do not depend on user-provided content. In the presence of bad memory, it's impossible for a program to proceed safely. Taking the machine out of service is the safest course of action. One of ten multi-threaded application servers behind a load balancer encounters a null pointer in business logic while processing a customer request. ✅ ❌ Your vote: My vote: ❌ Customer requests triggering bugs in business logic isn't a good reason to bring the whole server down. Instead, fail that particular request (returning an HTTP 5xx error), and continue with other user requests. In approaches like Erlang, or even Lambda, it may be the right approach to crash the whole application in response to a bad request, because this crash is handled at a higher layer in the architecture. This is also why I pr ## How Klarna Migrated the KRED System from Mnesia to Postgres with Zero Downtime DevFeed: [How Klarna Migrated the KRED System from Mnesia to Postgres with Zero Downtime]() Original publisher: [Read original article]() Author: Onno Vos Dev Published: 2025-02-26T09:04:27Z Content type: article Language: en Sources: [Klarna Engineering]() Topics: [Databases](), [Erlang](), [Replication](), [sharding](), [Transactions](), [systems]() Tags: [cluster](), [databases](), [erlang](), [klarna](), [memory](), [postgresql](), [production](), [replication](), [scaling](), [sharding](), [software-development](), [software-engineering](), [transactions]() ### AI overview This article describes Klarna's migration of KRED, an Erlang servicing system, from Mnesia to Postgres with zero downtime. It explains the original replicated seven-node architecture, the system's scaling challenges, and a plan involving sharding across multiple clusters. ### Source excerpt How we migrated from Mnesia to Postgres with zero downtime Back in December 2004, an Erlang application was born called KRED (referring to the freshly-started company called Kreditor, now known as Klarna). KRED is one of the "servicing systems" at Klarna and keeps track of consumer debt (among other things). It was powered by Mnesia and consisted of a cluster of 7 nodes, each holding a full copy of the database on disk. The data was replicated using a custom replication mechanism built in-house by Klarna. One node was elected as the leader and its database was considered the source of truth in the system. All database transactions were executed on the leader and writes were replicated to the rest of the nodes, the so-called followers. The Mnesia database was around 15 TB and at its peak in 2018 around 1.3 TB was held in memory at all times. Considering that few suppliers were selling hardware with such specs, it's easy to claim the crown of one of the biggest Mnesia databases in terms of in-memory storage, that was running in production. The rest of the data was offloaded to disk using mnesia_eleveldb. KRED has been a stable workhorse at Klarna so why change a winning concept? Get ready, for a two part blog post where we'll first go through our journey of how we went about this and secondly, how we made Mnesia behave just like Postgres and implemented our version serializable isolation level on top of Postgres! How the journey started Three engineers, sat down in a bar in Stockholm, Sweden and asked this question: 'When Klarna truly takes off, will KRED survive? Assuming "no", and presented with a blanco check, how would we tackle this problem?' The answer quickly revolved around the issues of running Mnesia on an even larger cluster and with leveldb compaction hitting some hot tables during peak times. One can only imagine how that problem would just continue to get worse over time. Considering the three engineers had worked on KRED for a long time, scaling KRED wa ## New Chainguard Images December 2024: Adoptium, AWX, CouchDB DevFeed: [New Chainguard Images December 2024: Adoptium, AWX, CouchDB]() Original publisher: [Read original article]() Published: 2025-01-16T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [Adoptium](), [openjdk](), [Ansible](), [Java](), [NoSQL](), [Open Source](), [Erlang](), [.NET MAUI](), [Process]() Tags: [adoptium](), [ansible](), [apache](), [awx](), [chainguard](), [chainguard-images](), [container-images](), [couchdb](), [erlang](), [helm](), [java](), [jdk](), [linkerd](), [net-11](), [nosql](), [open-source](), [opentofu]() ### AI overview Chainguard describes its December 2024 batch of 39 new Chainguard Images, highlighting images for Adoptium, AWX, and Apache CouchDB. The article notes FIPS-enabled variants and summarizes the intended uses and image characteristics. ### Source excerpt Chainguard released several new images in December 2024, including images for Adoptium, AWX, CouchDB, and others. Check out the full list. ## Elixir clustering using Postgres DevFeed: [Elixir clustering using Postgres]() Original publisher: [Read original article]() Author: Filipe Cabaço Published: 2024-01-09T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Elixir](), [Erlang](), [Supabase](), [Cloud](), [Latency]() Tags: [building](), [cloud](), [elixir](), [hosting](), [how-to](), [latency](), [learn](), [postgres](), [servers]() ### AI overview This article explains Supabase's open-source libcluster Postgres Strategy for connecting multiple Elixir nodes without introducing an additional service. It describes using Postgres NOTIFY and LISTEN to discover nodes, propagate address payloads, and support cluster formation and healing through libcluster. ### Source excerpt Learn about our approach to connecting multiple nodes in Elixir using Postgres ## Router 2.0 Common Runtime Router: The Road to Beta DevFeed: [Router 2.0 Common Runtime Router: The Road to Beta]() Original publisher: [Read original article]() Author: Elizabeth Cox Published: 2023-10-30T22:00:00Z Content type: article Language: en Sources: [Heroku]() Topics: [Heroku](), [Routing (disambiguation)](), [Erlang](), [servers](), [Concurrency](), [legacy](), [Scalability](), [Open Source]() Tags: [concurrency](), [engineering](), [erlang](), [http-server](), [legacy](), [modernization](), [open-source](), [release](), [router-2-0](), [routing](), [scalability]() ### AI overview Heroku describes the beta release of Router 2.0, a replacement for the existing Common Runtime router planned for 2024. The article explains the legacy router's Erlang-based architecture and the challenges that motivated a new implementation, including safer delivery of routing features and planned HTTP/2 support. ### Source excerpt Last month, Heroku announced the beta release of Router 2.0, the new Common Runtime router! As part of our commitment to infrastructure modernization, Heroku is making upgrades to the Common Runtime routing layer. The beta release of Router 2.0 is an important step along this journey. We're excited to give you an inside look at [...] The post Router 2.0 Common Runtime Router: The Road to Beta appeared first on Heroku. ## Hopping into spring with Chainguard's RabbitMQ Image DevFeed: [Hopping into spring with Chainguard's RabbitMQ Image]() Original publisher: [Read original article]() Published: 2023-02-24T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [Messaging](), [Security](), [Cloud Native Ecosystem](), [Containers](), [vulnerability scanning](), [Erlang](), [Open Source](), [GitHub]() Tags: [base-images](), [bazel](), [chainguard](), [chainguard-images](), [container-images](), [containers](), [cosign](), [cves](), [documentation](), [image](), [messaging](), [minimal-image](), [provenance](), [rabbitmq](), [rabbitmq-image](), [sboms](), [secure-images](), [security](), [slsa](), [software-supply-chain]() ### AI overview Chainguard announces a Chainguard Image for RabbitMQ, an open-source message broker used in cloud-native applications. The image is built from source on Wolfi, with custom Erlang and OTP components, continuous patching, minimal CVEs, SBOMs, signatures, and SLSA Build Level 2 provenance. ### Source excerpt Unlock advanced messaging capabilities with Chainguard's RabbitMQ image, designed for robustness and security. ## Taking Another Look at Phoenix and Elixir - Part 1 - Upgrading DevFeed: [Taking Another Look at Phoenix and Elixir - Part 1 - Upgrading]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-09-15T14:23:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Elixir](), [phoenix](), [Homebrew](), [Package manager](), [Erlang](), [Rails]() Tags: [elixir](), [erlang](), [homebrew](), [installation](), [phoenix](), [rails](), [tooling](), [upgrade]() ### AI overview A practical guide to upgrading Elixir, Erlang/OTP, Mix, Hex, and Phoenix, then creating a sample Phoenix application and preparing to compare it with an existing Rails codebase. ### Source excerpt I've been on the fence about Phoenix and Elixir for a while and I thought I'd take at least a quick dive. I've had a development system for Phoenix and Elixir since at least 2016 but I haven't done much. This means that the first task is bringing it into the 2020s. Upgrading Elixir I installed Elixir via HomeBrew which means it is a simple: which elixir /usr/local/bin/elixir Note: It can be hard sometimes to know if you installed things via HomeBrew and checking their location is an easy cheap as HomeBrew installs stuff to /usr/local/bin And then: brew upgrade elixir And then: elixir --version Erlang/OTP 23 [erts-11.0.3] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:1] [hipe] [dtrace] Elixir 1.10.4 (compiled with Erlang/OTP 23) You can also use just -v: elixir -v Erlang/OTP 23 [erts-11.0.3] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:1] [hipe] [dtrace] Elixir 1.10.4 (compiled with Erlang/OTP 23) Upgrading Mix and Hex Mix and Hex give the equivalent of a build tool (like Rake from the Rails world) and a Package Manager (like Gem / Bundler). To upgrade mix, you use: mix local.hex Found existing entry: /Users/sjohnson/.mix/archives/hex-0.20.5 Are you sure you want to replace it with "https://repo.hex.pm/installs/1.10.0/hex-0.20.5.ez"? [Yn] Y * creating /Users/sjohnson/.mix/archives/hex-0.20.5 And that will upgrade both mix and hex. Upgrading Phoenix The phoenix framework version I have dates back to 1.2 or 1.3 I think. The first step is to figure out what version I have: mix phoenix.new --version Phoenix v1.3.3 The method to upgrade the Phoenix framework itself is: mix archive.install hex phx_new 1.5.4 I used a google query to discover that the current Phoenix framework version was 1.5.4. The other way to find this version number is to go to this url: https://hexdocs.pm/phoenix/installation.html And then look at the drop down of different versions in the left hand sidebar. The latest version is always at the top. Creating a Sample App My fir ## Developer Spotlight: Postmates DevFeed: [Developer Spotlight: Postmates]() Original publisher: [Read original article]() Author: Richard Moot Published: 2019-08-14T10:00:00Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [API](), [Binance](), [Back end](), [Front end](), [React](), [Elixir](), [Erlang](), [Go](), [Python](), [Redux](), [Scala](), [TypeScript]() Tags: [api](), [apis](), [backend](), [developer](), [developer-velocity](), [elixir](), [erlang](), [frameworks](), [frontend](), [go](), [integration](), [java](), [kotlin](), [python](), [react](), [redux](), [scala](), [slack](), [spotlight](), [swift](), [typescript]() ### AI overview Square's developer spotlight features Postmates and discusses its integration with the Square Orders API, along with Postmates' engineering organization, development practices, and technology stack. ### Source excerpt Postmates talks with us about their integration of Orders API ## The Evolution of the Developer Retreat DevFeed: [The Evolution of the Developer Retreat]() Original publisher: [Read original article]() Author: Bruce Eckel Published: 2018-09-06T00:00:00Z Content type: opinion Language: en Sources: [Bruce Eckel - Computing Thoughts]() Topics: [Kotlin](), [Elixir](), [Flutter](), [Erlang](), [Android](), [iOS]() Tags: [android](), [conferences](), [developer](), [elixir](), [erlang](), [events](), [evolution](), [flutter](), [ios](), [kotlin](), [self-organizing]() ### AI overview The author reflects on a developer retreat that used no central theme or fixed structure. Participants worked independently, shared discussions, and explored Kotlin, Elixir, Erlang, and Flutter, among other topics. ### Source excerpt I've been experimenting with different forms of events for many years now. Mostly this has been in the form of self-organizing conferences, but in recent years I've tried going further, to even less structure. I've held a number of "developer retreats" where we had a theme that everyone focused on, and those have been quite interesting and valuable. To be honest, what I really wanted to try with the developer retreats is zero structure. ## Writing custom modules for Ansible DevFeed: [Writing custom modules for Ansible]() Original publisher: [Read original article]() Author: Wojtek Gawroński (afronski) Published: 2016-03-28T19:00:00Z Content type: tutorial Language: en Sources: [Wojtek Gawroński]() Topics: [Ansible](), [modules](), [Automation](), [configuration-management](), [Erlang](), [JSON](), [YAML](), [Scripting]() Tags: [ansible](), [automation](), [c-sharp](), [canvas](), [clojure](), [code](), [commands](), [configuration](), [configuration-management](), [css](), [css3](), [erlang](), [html](), [html5](), [javascript](), [json](), [modules](), [mono](), [net](), [node-js](), [programming](), [scripting](), [sicp](), [vagrant](), [webgl]() ### AI overview This tutorial explains Ansible modules, including their role in remote infrastructure management, YAML-based declarative configuration, dependencies on the provisioned machine, and JSON input/output requirements. It then introduces a case study for implementing a custom module in Erlang to process XML status pages. ### Source excerpt Writing custom modules for Ansible Introduction What is Ansible and what is a module? If you are a big fan of automation, if you are focused on spreading and building software in line with DevOps culture, tools related with automation / configuration management like Chef or Ansible are probably well known to you. From the other hand that what differentiates those tools is a topic for a next blog post. Without diving into those differences, let's briefly zoom into details for those people which do not know what Ansible and modules are. Ansible is a free-software platform for configuring and managing machines. It combines deployment, ad-hoc tasks execution and configuration management. This tool uses YAML and declarative way of defining steps, which are modifying state of your fleet. Module is a single piece of those steps, a well defined way of executing certain tasks on the remote infrastructure. It executes commands, and communicates by outputting JSON to standard output - it means that it can be written in any programming or scripting language. Development Before we'll start actual implementation we need to know how it works underneath. Requirements If you want to write a custom module, we stated above that you have to be aware of two things. Your module code will be executed on the provisioned machine, so all dependencies which your module requires, have to be there. Second, your module communicates over specific input and output protocols. It uses certain syntax for sending input parameters (either sent as a stdin or a file) and JSON protocol which will be consumed as an output of the module. And nothing more - any other, non-JSON compliant output will be treated as an error, and would not be consumed by Ansible properly. Case Study We would like to consume XMLified status pages and do certain actions based on checked and exposed facts, scraped from aforementioned place. Because I like Erlang, I will use that language to implement that module. We will do it usin ## My year in review - 2015 DevFeed: [My year in review - 2015]() Original publisher: [Read original article]() Author: Wojtek Gawroński (afronski) Published: 2015-12-31T15:00:00Z Content type: article Language: en Sources: [Wojtek Gawroński]() Topics: [Programming](), [Elixir](), [Microservices](), [phoenix](), [ClojureScript](), [Erlang](), [JavaScript](), [Node.js](), [Bash](), [C](), [Python](), [Ruby]() Tags: [blog](), [c-sharp](), [canvas](), [clojure](), [css](), [css3](), [erlang](), [html](), [html5](), [javascript](), [languages](), [microservices](), [mono](), [net](), [node-js](), [open-source](), [programming](), [sicp](), [vagrant](), [webgl](), [year-in-review]() ### AI overview A personal review of 2015 covering talks, meetups, blog posts, books, programming languages, and plans for 2016. It highlights work involving microservices, Elixir, Phoenix, Node.js, Erlang, ClojureScript, and several other languages. ### Source excerpt My year in review - 2015 Github Talks Nov 2015 - Evolution > Revolution - how should microservices be built? Sep 2015 - Elixir + Phoenix Jun 2015 - ZeroMQ in Node.js Apr 2015 - Erlang Ecosystem (PL) Feb 2015 - Elixir Feb 2015 - ClojureScript + Om = ♥ Details: My Talks Meetups Two meet-up groups created and continued in 2015: NodeSchool Silesia Silesian BEAMers Blog Most viewed blog posts by me Books List of book which I've read in 2015 and reading challenge. Favorite technical book of 2015 Pragmatic Thinking and Learning: Refactor Your Wetware - blog post about it Number of books read 20 Programming Favorite programming languages (or related) I've hacked on/with this year Languages with pet projects: Erlang #1, Erlang #2, Elixir #1, Elixir #2 ClojureScript Programming languages used for work-related projects this year JavaScript - ES 5 (Node.js, Front-End), JavaScript - ES6 (Front-End), Java, C, Ruby, Python, Bash Programming languages that I hope to explore next year Idris, Rust, Prolog Plans for 2016 Apply 100:10:1 rule to my open source work. Proceed with cost-benefit analysis and focus on monetization in terms of open source work. Try to kick-off another meet up in Silesia region - Papers We Love. Learning (even more than previously) about theory and how to design distributed and real-time systems. Focus on doing interactive blog posts and higher quality (premium?) materials. Push even harder work related with quality and visibility of blog posts. Take more time to discover new music. Happy New Year! :wink: ## Seven Languages in Seven Weeks: Erlang DevFeed: [Seven Languages in Seven Weeks: Erlang]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2012-12-18T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Erlang](), [Concurrency](), [function](), [pattern matching](), [Processes]() Tags: [concurrency](), [erlang](), [function](), [pattern-matching](), [process](), [recursion]() ### AI overview A beginner documents working through Erlang exercises from "Seven Languages in Seven Weeks," covering recursion, pattern matching, list comprehensions, regular expressions, concurrency, process monitoring, and process restarts. The author notes that some solutions may contain errors while learning the language. ### Source excerpt So, I just bought "Seven Languages in Seven Weeks". I've read the Ruby chapter, not a big deal at all, so I skipped it. I also skip Io, Prolog and Scala (for now), and then, fall in Erlang! ## Tsung: An Open-Source Distributed Load-Testing Tool for Multiple Protocols DevFeed: [Tsung: An Open-Source Distributed Load-Testing Tool for Multiple Protocols]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2011-08-02T08:30:00Z Content type: article Language: en Sources: [Dimitri Fontaine]() Topics: [Testing](), [Benchmark](), [Erlang](), [PostgreSQL](), [Protocol (disambiguation)](), [sessions](), [Open Source](), [Development]() Tags: [benchmark](), [erlang](), [load-testing](), [open-source](), [postgresql](), [protocol](), [sessions](), [testing]() ### AI overview The article introduces Tsung, an open-source, multi-protocol distributed load-testing tool built with Erlang. It describes benchmarking applications, recording and replaying sessions at high scale, PostgreSQL support, and integration with pgfouine for converting PostgreSQL logs into Tsung sessions. It also mentions the uTsung variant used in video games and a video demo. ### Source excerpt Tsung is an open-source multi-protocol distributed load testing tool and a mature project. It's been available for about 10 years and is built with the Erlang system. It supports several protocols, including the PostgreSQL one. When you want to benchmark your own application, to know how many more clients it can handle or how much gain you will see with some new shiny hardware, Tsung is the tool to use. It will allow you to record a number of sessions then replay them at high scale. pgfouine supports Tsung and is able to turn your PostgreSQL logs into Tsung sessions, too. ## BigWig: A better Erlang webtool (spawnfest entry) DevFeed: [BigWig: A better Erlang webtool (spawnfest entry)]() Original publisher: [Read original article]() Author: {"image"=\>"rj-headshot.jpg", "greetings"=\>nil} Published: 2011-07-11T05:00:00Z Content type: article Language: en Sources: [Richard Jones]() Topics: [Erlang](), [Programming](), [Web](), [WebSocket](), [systems]() Tags: [appmon](), [architecture](), [erlang](), [etop](), [json](), [processes](), [programming](), [realtime](), [sasl](), [spawnfest](), [web](), [webtool]() ### AI overview The article describes BigWig, a web-based suite of Erlang tools created during Spawnfest. It presents process inspection, process information, application hierarchy exploration, SASL report browsing, and VM dashboards, using Cowboy and WebSockets; some parts were unfinished. ### Source excerpt This weekend, Steve, Hunter, Paul and I took part in Spawnfest, a 48-hour Erlang programming event. ## Erlang rebar tutorial: generating releases and upgrades DevFeed: [Erlang rebar tutorial: generating releases and upgrades]() Original publisher: [Read original article]() Author: {"image"=\>"rj-headshot.jpg", "greetings"=\>nil} Published: 2011-03-26T05:00:00Z Content type: tutorial Language: en Sources: [Richard Jones]() Topics: [Erlang](), [Tutorial](), [releases](), [Development](), [make]() Tags: [appup](), [code](), [deploy](), [development](), [erlang](), [gnu-linux](), [make](), [otp](), [production](), [programming](), [project](), [rebar](), [releasehandler](), [releases](), [sasl](), [tutorial](), [upgrades]() ### AI overview A tutorial on using rebar to structure, compile, package, deploy, and upgrade Erlang applications. It demonstrates creating releases that bundle the Erlang VM, required OTP libraries, application code, and dependencies, enabling installation of new versions without downtime. ### Source excerpt During my experiments with rebar, I made a simple example app for testing upgrades and releases. This article will walk you through using rebar to create an application, lay it out properly, package and deploy it, and create and install new versions without downtime. ## Erlang/OTP releases: rebar, release\_handler, .appup, etc DevFeed: [Erlang/OTP releases: rebar, release\_handler, .appup, etc]() Original publisher: [Read original article]() Author: {"image"=\>"rj-headshot.jpg", "greetings"=\>nil} Published: 2010-09-18T05:00:00Z Content type: opinion Language: en Sources: [Richard Jones]() Topics: [Erlang](), [releases](), [upgrade](), [modules]() Tags: [appup](), [deployment](), [erlang](), [hacks](), [irc](), [irccloud](), [mochiweb](), [otp](), [programming](), [release](), [releases](), [sasl](), [sysops](), [upgrade]() ### AI overview An Erlang developer describes deploying live upgrades for running OTP applications behind an in-browser IRC client. The article discusses release packaging, release_handler, .appup files, rebar, and an upgrade from R13B to R14 after encountering upgrade-related problems. ### Source excerpt I've been building something in Erlang recently, provisionally called IRCCloud.com (mention this post if you request an invite!) - it's an in-browser IRC client that stays connected for you all the time, so you never miss the conversation. You can reopen your browser later and still have all the backlog. IRC is damn useful, and James and I are building IRCCloud to give you the advantages of IRC bouncer-esque functionality, with the ease of just opening a webpage. ## Background writers DevFeed: [Background writers]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2010-07-19T14:30:00Z Content type: opinion Language: en Sources: [Dimitri Fontaine]() Topics: [PostgreSQL](), [Processes](), [Erlang](), [Finite-state machine]() Tags: [article](), [database](), [erlang](), [postgresql](), [processes](), [worker]() ### AI overview The article discusses proposals to generalize PostgreSQL background workers, building on the autovacuum process and related patches. It considers an extensibility API for external processes and workers, drawing ideas from Erlang supervision and finite-state-machine behaviors. ### Source excerpt There's currently a thread on hackers about bg worker: overview and a series of 6 patches. Thanks a lot Markus! This is all about generalizing a concept already in use in the autovacuum process, where you have an independent subsystem that require having an autonomous daemon running and able to start its own workers. I've been advocating about generalizing this concept for awhile already, in order to have postmaster able to communicate to subsystems when to shut down and start and reload, etc. Some external processes are only external because there's no need to include them by default in to the database engine, not because there's no sense to having them in there. ## Rewriting Playdar from C++ to Erlang: source-code savings and similar resource use DevFeed: [Rewriting Playdar from C++ to Erlang: source-code savings and similar resource use]() Original publisher: [Read original article]() Author: {"image"=\>"rj-headshot.jpg", "greetings"=\>nil} Published: 2009-10-21T05:00:00Z Content type: opinion Language: en Sources: [Richard Jones]() Topics: [Erlang](), [C++](), [Code](), [cross-platform](), [Optimization]() Tags: [c](), [c-plus-plus](), [code](), [cross-platform](), [erlang](), [optimization](), [playdar](), [programming](), [rewrite]() ### AI overview The author describes rewriting Playdar from C++ to Erlang after initially developing it with Boost, Asio, and CMake. The Erlang version reached near feature parity within a week, and counting bundled third-party code while excluding Boost and Asio showed a 92% reduction in source lines. Preliminary comparisons found similar CPU and memory usage overall, with Erlang using slightly more memory at the time of writing. ### Source excerpt I've heard many anecdotes and claims about how many lines of code are saved when you write in Erlang instead of [C++/other language]. I'm happy to report that I now have first-hand experience and some data to share. ## Erlang talk at London Hackspace DevFeed: [Erlang talk at London Hackspace]() Original publisher: [Read original article]() Author: {"image"=\>"rj-headshot.jpg", "greetings"=\>nil} Published: 2009-10-08T05:00:00Z Content type: article Language: en Sources: [Richard Jones]() Topics: [Erlang](), [Programming](), [Functional programming](), [Processes]() Tags: [code](), [distributed-systems](), [erlang](), [functional-programming](), [hackspace](), [london](), [messages](), [mochiweb](), [playdar](), [processes](), [recursion](), [state](), [talk](), [uncategorized](), [upgrade]() ### AI overview This article recaps an introductory Erlang talk at a London Hackspace meetup. It explains Erlang's use for scalable, reliable distributed systems and demonstrates processes, message passing, recursive state management, hot code reloading, and gen_server. ### Source excerpt Last night I gave an "Intro to Erlang" talk at a London Hackspace meetup. I did a quick audience survey first: About 75% did "web programming" (ruby,python,php,etc). Around 30% admitted to regularly using C/C++/Java or desktop/mobile app development. Less than 10% had much experience with functional programming.