# 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.

## Build a serverless recipe-sharing API with Go and Amazon Aurora DSQL

DevFeed: [Build a serverless recipe-sharing API with Go and Amazon Aurora DSQL](<https://devfeed.tech/articles/build-a-serverless-recipe-sharing-api-with-go-and-amazon-aurora-dsql-131173.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/build-a-serverless-recipe-sharing-api-with-go-and-amazon-aurora-dsql/>)

Author: Steve Brown

Published: 2026-11-12T16:14:20Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [DSQL](<https://devfeed.tech/topics/dsql.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>)

Tags: [amazon-api-gateway](<https://devfeed.tech/tags/amazon-api-gateway.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [cloudformation](<https://devfeed.tech/tags/cloudformation.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [distribution](<https://devfeed.tech/tags/distribution.md>), [dsql](<https://devfeed.tech/tags/dsql.md>), [go](<https://devfeed.tech/tags/go.md>), [iam](<https://devfeed.tech/tags/iam.md>), [integrity](<https://devfeed.tech/tags/integrity.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [keys](<https://devfeed.tech/tags/keys.md>), [optimistic-concurrency](<https://devfeed.tech/tags/optimistic-concurrency.md>), [recipe](<https://devfeed.tech/tags/recipe.md>), [referential-integrity](<https://devfeed.tech/tags/referential-integrity.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [retries](<https://devfeed.tech/tags/retries.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [token](<https://devfeed.tech/tags/token.md>), [uuid](<https://devfeed.tech/tags/uuid.md>)

### AI overview

The article demonstrates a Go recipe-sharing REST API that runs locally as a Gin HTTP server or on AWS Lambda behind API Gateway, using the same handlers and an Amazon Aurora DSQL store. It describes UUID text primary keys to spread writes across storage partitions; short-lived IAM tokens, TLS, and a pgx connection pool managed by the Go connector; and separate DDL operations because DDL and DML cannot share a transaction. The sample checks chef and recipe references in handlers, though the database can enforce them with foreign keys instead. Aurora DSQL optimistic concurrency conflicts can be retried by the connector's occretry package with exponential backoff, so transaction logic should be idempotent. Deployment uses a script and CloudFormation for Lambda, API Gateway, IAM, and logs; its IP allowlist is not authentication, and the article recommends adding an authorization method for production. The text also notes connection recycling before the 60-minute server limit and low pool sizing for single-request Lambda invocations.

### Source excerpt

Build a fully serverless recipe-sharing REST API in Go on Amazon Aurora DSQL, AWS Lambda, and Amazon API Gateway. Learn UUID primary keys for even write distribution, short-lived IAM token authentication, application-layer referential integrity, and automatic optimistic-concurrency retries, with a one-command CloudFormation deployment.

## Effect 4.0 Ships: Dependency-Free Rewrite with 5x Smaller Bundles and Long-Term Support

DevFeed: [Effect 4.0 Ships: Dependency-Free Rewrite with 5x Smaller Bundles and Long-Term Support](<https://devfeed.tech/articles/effect-4-0-ships-dependency-free-rewrite-with-5x-smaller-bundles-and-long-term-support-124957.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/effect-4-0-release/>)

Author: Daniel Curtis

Published: 2026-11-10T06:33:00Z

Content type: release

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Erlang](<https://devfeed.tech/topics/erlang.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>)

Tags: [dependencies](<https://devfeed.tech/tags/dependencies.md>), [dependency-injection](<https://devfeed.tech/tags/dependency-injection.md>), [development](<https://devfeed.tech/tags/development.md>), [effect](<https://devfeed.tech/tags/effect.md>), [effect-4-0-release](<https://devfeed.tech/tags/effect-4-0-release.md>), [fiber](<https://devfeed.tech/tags/fiber.md>), [framework](<https://devfeed.tech/tags/framework.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [news](<https://devfeed.tech/tags/news.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [september-2026](<https://devfeed.tech/tags/september-2026.md>), [size](<https://devfeed.tech/tags/size.md>), [structured-concurrency](<https://devfeed.tech/tags/structured-concurrency.md>), [throughput](<https://devfeed.tech/tags/throughput.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [web-development](<https://devfeed.tech/tags/web-development.md>)

### AI overview

Effect 4.0 rewrites Effect's fiber runtime and consolidates core ecosystem modules in the `effect` package, which now has zero runtime dependencies. The team reports a minimal bundle shrinking from 35.6 kB to 7.1 kB, memory for 50,000 fibers falling from 157.5 MB to 21.8 MB, and throughput rising from 0.71 million to 4.57 million tasks per second. These are medians of nine fresh-process runs on identical source and have not been independently reproduced. Effect 4.x receives bug fixes through September 2029 or one year after 5.0 ships, whichever is later; security fixes follow the same date or two years after 5.0. Early patches added missing stability tags to modules that had shipped without them. A v3-to-v4 migration guide is available.

### Source excerpt

Effect 4.0, a TypeScript framework for typed errors and structured concurrency, was released on 30 September 2026 with a rewritten fiber runtime. The team reports a bundle size drop from 35.6 kB to 7.1 kB and about 6.4x higher throughput, though these figures are not independently verified. It also adds long-term support through September 2029. By Daniel Curtis

## Longtail-SWE: High-Quality SWE Tasks for Underrepresented Languages

DevFeed: [Longtail-SWE: High-Quality SWE Tasks for Underrepresented Languages](<https://devfeed.tech/articles/longtail-swe-high-quality-swe-tasks-for-underrepresented-languages-125913.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.10304>)

Author: Vladimir Dobrovolskii, Ibragim Badertdinov, Alexander Golubev

Published: 2026-11-10T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Benchmark](<https://devfeed.tech/topics/benchmark.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [Haskell](<https://devfeed.tech/topics/haskell.md>), [IntelliJ IDEA](<https://devfeed.tech/topics/intellij-idea.md>), [The Julia Language](<https://devfeed.tech/topics/julia.md>), [Swift](<https://devfeed.tech/topics/swift.md>), [Frontier AI](<https://devfeed.tech/topics/frontier-ai.md>)

Tags: [benchmark](<https://devfeed.tech/tags/benchmark.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [programming-language](<https://devfeed.tech/tags/programming-language.md>), [quality](<https://devfeed.tech/tags/quality.md>), [tasks](<https://devfeed.tech/tags/tasks.md>)

### AI overview

Longtail-SWE provides 202 repository-level issue-resolution tasks across 13 languages with limited representation in existing benchmarks. To vet candidates without discarding challenging problems, its solver-judge-repairer pipeline has a solver attempt each task, then a judge review the task, solver trajectory, and test results to guide repairs to tests and descriptions. The revisions target tests that reject valid alternatives or accept incorrect solutions while preserving task requirements. The authors evaluate nine model configurations, including frontier models, on solving performance, consistency across repeated attempts, and resource use. They release the tasks, executable environments, construction and evaluation tools, agent trajectories, and an easier task set for smaller models.

### Source excerpt

arXiv:2611.10304v1 Announce Type: cross Abstract: Challenging repository-level benchmarks remain limited for many programming language ecosystems, where filtering scarce candidates with ambiguous descriptions or defective tests can discard valuable engineering problems. We introduce Longtail-SWE, a benchmark of 202 issue-resolution tasks across 13 languages with limited coverage in existing repository-level benchmarks: Clojure, Dart, Elixir, Erlang, F#, Haskell, Julia, Kotlin, Lua, OCaml, R, Scala, and Swift. Its construction uses a solver--judge--repairer pipeline: a solver attempts each candidate task, and a judge reviews the task together with the solver's trajectory and test results to guide revisions to tests and task descriptions. These revisions aim to correct tests that reject valid alternative implementations or accept incorrect solutions while retaining challenging tasks and preserving their intended requirements. We evaluate nine model configurations, including frontier models, and analyze task-solving performance, consistency across repeated attempts, and resource usage. We release all benchmark instances, executable environments, complete construction and evaluation tooling, and agent trajectories, together with an additional set of easier tasks to support evaluation of smaller models.

## Gleam doesn't compile to Erlang source anymore

DevFeed: [Gleam doesn't compile to Erlang source anymore](<https://devfeed.tech/articles/gleam-doesn-t-compile-to-erlang-source-anymore-64919.md>)

Original publisher: [Read original article](<https://gleam.run/news/gleam-doesnt-compile-to-erlang-source-anymore>)

Author: Louis Pilfold

Published: 2026-10-05T00:00:00Z

Content type: release

Language: en

Sources: [Gleam](<https://devfeed.tech/sources/gleam.md>)

Topics: [Compiler](<https://devfeed.tech/topics/compiler.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [Code generation](<https://devfeed.tech/topics/code-generation.md>), [Parsing](<https://devfeed.tech/topics/parsing.md>)

Tags: [beam](<https://devfeed.tech/tags/beam.md>), [build-times](<https://devfeed.tech/tags/build-times.md>), [code-generator](<https://devfeed.tech/tags/code-generator.md>), [code-quality](<https://devfeed.tech/tags/code-quality.md>), [compilation](<https://devfeed.tech/tags/compilation.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [debuggers](<https://devfeed.tech/tags/debuggers.md>), [encoding](<https://devfeed.tech/tags/encoding.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [gleam](<https://devfeed.tech/tags/gleam.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [performance](<https://devfeed.tech/tags/performance.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [source-code](<https://devfeed.tech/tags/source-code.md>), [syntax](<https://devfeed.tech/tags/syntax.md>), [type-safe](<https://devfeed.tech/tags/type-safe.md>), [virtual-machine](<https://devfeed.tech/tags/virtual-machine.md>)

### AI overview

Gleam v1.19.0 rewrites its Erlang code generator to emit Erlang abstract forms, which the Erlang compiler can load directly, skipping its tokenizer and parser. The article reports faster Erlang builds and runtime location metadata that points accurately to Gleam source, improving crash reports and stack traces; debugger support such as edb is described as a possibility, not completed work. It favors abstract forms over direct BEAM bytecode because bytecode changes across VM releases, and reproducing Erlang compiler optimizations would take substantial ongoing effort. The release also flattens generated JavaScript for pattern matches, improves short-list construction while retaining array conversion for longer lists, preserves TypeScript generic types through overloads, adds build-tool support including generated `.app` files and a `--no-dev` flag, and adds language-server label operations, browser formatting capability, and more targeted errors. Its compilation benchmark compares a small synthetic workload and is explicitly limited; it cannot establish performance across real projects.

### Source excerpt

Gleam is a type-safe and scalable language for the Erlang virtual machine and JavaScript runtimes. Today Gleam v1.19.0 has been published, so let's go over what's new. A new compilation target Over the last few months Giacomo Cavalieri has entirely rewritten Gleam's Erlang code generator that has an entirely different design, and most notably, outputs a different format. Previously Gleam generated Erlang source code, now it generates Erlang abstract forms. "Erlang abstract forms" is an intermediate representation used by the Erlang compiler. It is a metadata-annotated tree that represents Erlang syntax, and it is normally produced by running Erlang's tokeniser and parser. It has a binary encoding using Erlang's external term format, and with this binary format we can load our generated code directly, skipping the front-half of the Erlang compiler. This new Erlang code generator brings several benefits: The performance of the compiler has been improved, significantly reducing the build times for Gleam projects running on Erlang. The location metadata available to the runtime is now accurate to original Gleam source code, rather than to the Erlang source code the compiler would generate. This means, for example, the line numbers in BEAM crash reports and stacktraces are perfectly accurate, while previously they could be inaccurate, only pointing to the nearest function. This metadata could also enable full support for Gleam in debuggers such as edb, though we have not done any work on this ourselves. The code-quality of the Gleam compiler has been improved. The Erlang code generator was one of the oldest and most stable parts of the Gleam codebase, so while it wasn't causing us any problems it wasn't conforming to the standards and conventions we have today. This new replacement is excellent, and arguably raising the bar for the compiler as whole. We never have to hear someone use the word "transpiler" as a pejorative ever again.1 Ok, so how fast is it? I'm going to s

## The Strange Programming Language That Helped Build WhatsApp

DevFeed: [The Strange Programming Language That Helped Build WhatsApp](<https://devfeed.tech/articles/the-strange-programming-language-that-helped-build-whatsapp-62276.md>)

Original publisher: [Read original article](<https://hackernoon.com/the-strange-programming-language-that-helped-build-whatsapp?source=rss>)

Author: Bruce Li

Published: 2026-09-29T19:00:36Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Erlang](<https://devfeed.tech/topics/erlang.md>), [Programming language](<https://devfeed.tech/topics/programming-language.md>), [Programming](<https://devfeed.tech/topics/programming.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [discord](<https://devfeed.tech/tags/discord.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [gleam](<https://devfeed.tech/tags/gleam.md>), [hackernoon-top-story](<https://devfeed.tech/tags/hackernoon-top-story.md>), [language](<https://devfeed.tech/tags/language.md>), [programming-language](<https://devfeed.tech/tags/programming-language.md>), [rabbitmq](<https://devfeed.tech/tags/rabbitmq.md>), [scalability](<https://devfeed.tech/tags/scalability.md>), [whatsapp](<https://devfeed.tech/tags/whatsapp.md>)

### AI overview

A narrative account of Erlang's origins and its role in supporting WhatsApp at large scale. The supplied excerpt says WhatsApp handled tens of billions of messages a day with an engineering staff of around fifty, and traces Erlang to a Swedish telecom lab in the 1980s.

### Source excerpt

Erlang: a programming language built in a Swedish telecom lab in the 1980s, ended up running the biggest messaging app WhatsApp. Told by its co-creator.

## App Engine Flex Language Shootout

DevFeed: [App Engine Flex Language Shootout](<https://devfeed.tech/articles/app-engine-flex-language-shootout-27376.md>)

Original publisher: [Read original article](<http://engineering.khanacademy.org/posts/flex-language-shootout.htm>)

Author: Khan Academy

Published: 2017-04-17T22:00:00Z

Content type: article

Language: en

Sources: [Khan Academy](<https://devfeed.tech/sources/khan-academy.md>)

Topics: [Python](<https://devfeed.tech/topics/python.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [algorithm](<https://devfeed.tech/tags/algorithm.md>), [all](<https://devfeed.tech/tags/all.md>), [all-in](<https://devfeed.tech/tags/all-in.md>), [also](<https://devfeed.tech/tags/also.md>), [alternatives](<https://devfeed.tech/tags/alternatives.md>), [am](<https://devfeed.tech/tags/am.md>), [apis](<https://devfeed.tech/tags/apis.md>), [app](<https://devfeed.tech/tags/app.md>), [argument](<https://devfeed.tech/tags/argument.md>), [away](<https://devfeed.tech/tags/away.md>), [backend](<https://devfeed.tech/tags/backend.md>), [engine](<https://devfeed.tech/tags/engine.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [flex](<https://devfeed.tech/tags/flex.md>), [i](<https://devfeed.tech/tags/i.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [language](<https://devfeed.tech/tags/language.md>), [news](<https://devfeed.tech/tags/news.md>), [silicon](<https://devfeed.tech/tags/silicon.md>), [silicon-valley](<https://devfeed.tech/tags/silicon-valley.md>), [this](<https://devfeed.tech/tags/this.md>), [time](<https://devfeed.tech/tags/time.md>)

### AI overview

The hackathon project compared microservices in Elixir, Go, Kotlin, Python, and Crystal on App Engine Flex. Each was meant to validate a signed Pub/Sub message, parse it, and write exercise data to BigQuery through a web server. The benchmark was explicitly rough and incomplete: message validation was not implemented across all services, and the team measured how far services fell behind a Pub/Sub firehose and how quickly they cleared the backlog. Crystal could not be benchmarked because of unresolved SSL errors. Elixir nearly kept pace with Kotlin, but the results did not make a strong case for leaving Python. The author says Google Cloud Platform library quality may matter more than speed for this workload, and suggests that pull-based consumption could allow batched BigQuery inserts, making algorithm choice a possible performance gain. The work provided practical App Engine Flex experience and suggested microservices can work for a simple task bounded by external APIs, but did not settle Khan Academy's language strategy.

### Source excerpt

By Amos Latteier This is the second time I've been to Silicon Valley. Some years ago - never ... Read more

## Single file Gleam BEAM programs with escript

DevFeed: [Single file Gleam BEAM programs with escript](<https://devfeed.tech/articles/single-file-gleam-beam-programs-with-escript-51510.md>)

Original publisher: [Read original article](<https://gleam.run/news/single-file-gleam-beam-programs-with-escript>)

Author: Louis Pilfold

Published: 2026-06-02T00:00:00Z

Content type: release

Language: en

Sources: [Gleam](<https://devfeed.tech/sources/gleam.md>)

Topics: [Erlang](<https://devfeed.tech/topics/erlang.md>), [Build tool](<https://devfeed.tech/topics/build-tool.md>), [modules](<https://devfeed.tech/topics/modules.md>), [Compilers and Linkers](<https://devfeed.tech/topics/compilers-and-linkers.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Bun](<https://devfeed.tech/topics/bun.md>)

Tags: [beam](<https://devfeed.tech/tags/beam.md>), [bytecode](<https://devfeed.tech/tags/bytecode.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [file](<https://devfeed.tech/tags/file.md>), [gleam](<https://devfeed.tech/tags/gleam.md>), [modules](<https://devfeed.tech/tags/modules.md>), [v1](<https://devfeed.tech/tags/v1.md>)

### AI overview

Gleam v1.17.0 adds `gleam export escript` for BEAM projects: it compiles the project, checks for a valid `main` function, and packages compiled modules into one executable file for computers with Erlang installed. The release also adds language-server highlighting for variable references, permits `todo` in constants so incomplete code can still be type checked, and improves editor actions and compiler suggestions. Other changes include quieter `gleam dev` output, an outdated-dependency count, better Git detection when publishing from a monorepo, JavaScript pattern-matching optimizations, and fixes for configuration-validation vulnerabilities. The supplied text also describes improved record hovers and code actions for record updates, patterns, operators, and missing modules.

### Source excerpt

Gleam is a type safe and scalable language for the Erlang virtual machine and JavaScript runtimes. Today Gleam v1.17.0 has been published. Gleam Gathering But first: the first videos from the first ever all-Gleam conference have been released! You can view them on the Gleam Gathering YouTube account. The event was a roaring success and loads of fun. Stay tuned for news of the next one in 2027! Right, back to the release coverage. BEAM escripts When running on the Erlang virtual machine Gleam code is compiled to a series of .beam files, each of which contains the bytecode for a single Gleam module. This works fine for programs distributed or installed using package managers, containers, or other such systems, but having many files to share is a little inconvenient for sharing small command-line programs. In the JavaScript world this problem is solved using a "bundler", a program that takes many JavaScript modules and combines them into a single file. This single file can be copied to and run on any computer that has a JavaScript runtime installed (such as NodeJS, Deno, or Bun). Erlang has a similar solution: escripts. Much like a JavaScript bundle, an escript is a single file that contains all the modules of a program in the form of pre-compiled bytecode, and it can be run on any computer that has Erlang installed. The Erlang build tool has a convenient command for creating an escript, but for Gleam programmers the escript creation process has not been as straightforward. This release brings the gleam export escript command, which will compile the project, verify it has a valid main function, and build the escript file from the compiled bytecode. louis ~/src/my_project $ gleam export escript Compiling gleam_stdlib Compiling my_project Compiled in 0.48s Your escript has been generated to /home/louis/src/my_project/my_project. louis ~/src/my_project $ ./my_project Hello from my_project! Highlight references Gleam's language server provides IDE functionality for all edi

## JavaScript source maps

DevFeed: [JavaScript source maps](<https://devfeed.tech/articles/javascript-source-maps-51507.md>)

Original publisher: [Read original article](<https://gleam.run/news/javascript-source-maps>)

Author: Louis Pilfold

Published: 2026-04-24T00:00:00Z

Content type: release

Language: en

Sources: [Gleam](<https://devfeed.tech/sources/gleam.md>)

Topics: [Compilers and Linkers](<https://devfeed.tech/topics/compilers-and-linkers.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [typesafety](<https://devfeed.tech/topics/typesafety.md>), [Build tool](<https://devfeed.tech/topics/build-tool.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Transpilers](<https://devfeed.tech/topics/transpilers.md>), [IntelliJ IDEA](<https://devfeed.tech/topics/intellij-idea.md>)

Tags: [breakpoint](<https://devfeed.tech/tags/breakpoint.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [debug](<https://devfeed.tech/tags/debug.md>), [debuggers](<https://devfeed.tech/tags/debuggers.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [dev-tools](<https://devfeed.tech/tags/dev-tools.md>), [exception](<https://devfeed.tech/tags/exception.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [maps](<https://devfeed.tech/tags/maps.md>), [safari](<https://devfeed.tech/tags/safari.md>), [source](<https://devfeed.tech/tags/source.md>)

### AI overview

Gleam v1.16.0 adds JavaScript source maps so browser tools can show original Gleam locations in code, stack traces, and debugging sessions; enable them with `javascript.source_maps = true` and serve the generated map files. Serving the build directory or using Lustre's dev-tools already handles that. The release also improves language-server fault tolerance by reporting imports that lead to compilation failures and continuing with compilable module branches. Other changes include nearly 30% faster single-character string-prefix matching in the cited `glance` benchmark, a warning for JavaScript integer patterns wider than its 52-bit precision limit, package owner management, and additional code actions and compiler improvements.

### Source excerpt

Gleam is a type safe and scalable language for the Erlang virtual machine and JavaScript runtimes. Today Gleam v1.16.0 has been published, let's go over what's new. Gleam gets source maps Gleam's robust type system makes runtime errors very rare, but it would be naive to say that it's never necessary to debug Gleam code at runtime. When compiling code to JavaScript one challenge for runtime debugging is that the error and the source code shown is that of the compiled JavaScript, not the Gleam the programmer actually wrote. The solution to this problem is source maps, additional files that Gleam's compiler can now generate, teaching browsers and JavaScript runtimes what the original code is and how it maps on to the JavaScript it runs. Here it is in action with Safari's dev-tools: As you may know, it's not limited to just displaying the code, it also translates exception stack traces to the original locations, and enables use of breakpoints and debuggers. To enable source maps set the javascript.source_maps property to true in your gleam.toml, and ensure that you are serving these new files to the web browser along with your JavaScript code. If you are serving the build directory or using Lustre's dev-tools then there's nothing else to do. name = "my_project" version = "1.0.0" [javascript] source_maps = true [dependencies] gleam_stdlib = ">= 1.0.0 and < 2.0.0" A huge thank you to Ameen Radwan for this big improvement. Folks who enjoy breakpoint debugging will be especially pleased. Package-level fault tolerance Gleam is a fully-typed language, so to compile a module of Gleam code the compiler must first successfully compile all the modules it imports in order to have the required type information. Attempting to analyse modules without this information would result in a cascading failure of incorrect and misleading error messages, so when a module cannot be compiled the build tool stops and reports the errors. This behaviour successfully prevents the error cascade, bu

## The happy holidays release 2025 🎁

DevFeed: [The happy holidays release 2025 🎁](<https://devfeed.tech/articles/the-happy-holidays-release-2025-51511.md>)

Original publisher: [Read original article](<https://gleam.run/news/the-happy-holidays-2025-release>)

Author: Louis Pilfold

Published: 2025-12-25T00:00:00Z

Content type: release

Language: en

Sources: [Gleam](<https://devfeed.tech/sources/gleam.md>)

Topics: [Functional programming](<https://devfeed.tech/topics/functional-programming.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [TypeScript](<https://devfeed.tech/topics/typescript.md>), [export](<https://devfeed.tech/topics/export.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [annotation](<https://devfeed.tech/tags/annotation.md>), [annotations](<https://devfeed.tech/tags/annotations.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [ecosystems](<https://devfeed.tech/tags/ecosystems.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [external](<https://devfeed.tech/tags/external.md>), [holidays](<https://devfeed.tech/tags/holidays.md>), [interoperability](<https://devfeed.tech/tags/interoperability.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [language](<https://devfeed.tech/tags/language.md>), [release](<https://devfeed.tech/tags/release.md>), [runtimes](<https://devfeed.tech/tags/runtimes.md>), [static-analysis](<https://devfeed.tech/tags/static-analysis.md>), [type-safe](<https://devfeed.tech/tags/type-safe.md>), [types](<https://devfeed.tech/tags/types.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [v1](<https://devfeed.tech/tags/v1.md>)

### AI overview

Gleam v1.14.0 improves interoperability, compiler analysis, and developer tooling across Erlang, JavaScript, and the BEAM ecosystem. External types can now use `@external` annotations to generate precise Erlang and TypeScript definitions instead of vague `any` types. Pattern analysis adds interference based pruning for integer segments and canonical number normalization, helping optimize matches and detect unreachable clauses. The compiler also improves error locations and recovery from errors, warns about empty modules and detached documentation, and supports record updates in constants. JavaScript equality checks for fieldless custom variants are faster. Language server updates include type ranked autocomplete, broader refactoring actions, more useful diagnostics, and annotation generation for all top level definitions. Build tool additions include `gleam deps outdated`, clearer missing Git errors, updated Elixir compiler API support, and CLI refinements.

### Source excerpt

Merry Christmas and happy holidays everyone! Gleam is a type-safe and scalable language for the Erlang virtual machine and JavaScript runtimes. Gleam v1.14.0 is our Xmas gift for you, let's unwrap it and take a look inside. External annotations for external types Gleam doesn't exist in a vacuum, instead builds upon the existing Erlang and JavaScript ecosystems. It's not uncommon for Gleam programs and libraries to internally make use of code written in other languages in the same ecosystem, and Gleam code can be called from those languages too. To help with the interoperability between these languages the Gleam compiler can generate Erlang type specifications and TypeScript declaration files. These can be used with external type checkers and static analysis tooling to ensure the various languages are calling each other's code correctly. // Function written in Gleam pub fn greet(name: String) -> String { "Hello, " <> name <> "!" } % Generated Erlang type spec -spec greet(binary()) -> binary(). // Generated TypeScript type definition export function greet(name: string): string; When writing bindings to code in other languages, Gleam's external type feature is used to declare a type that can be referenced in Gleam, but since it originates from outside of Gleam it has an unknown shape and cannot be constructed directly. A very useful feature for designing Gleam-y APIs for external code! The limitation here was that due to Gleam not knowing anything about these external types, it was not able to produce a precise definition in generated Erlang or TypeScript type definitions, having to fall back to the correct but vague "any" type of each language. The @external annotation is now supported for external types, giving the programmer a way to specify an Erlang or TypeScript type definition to be used. For example, the Dict type from the standard library can now be written as the following: // External type declared in Gleam @external(erlang, "erlang", "map") @external(javasc

## What Now? Handling Errors in Large Systems

DevFeed: [What Now? Handling Errors in Large Systems](<https://devfeed.tech/articles/what-now-handling-errors-in-large-systems-12583.md>)

Original publisher: [Read original article](<http://brooker.co.za/blog/2025/11/20/what-now.html>)

Author: Marc Brooker

Published: 2025-11-20T00:00:00Z

Content type: article

Language: en

Sources: [Marc Brooker's](<https://devfeed.tech/sources/marc-brooker-s-blog.md>)

Topics: [systems](<https://devfeed.tech/topics/systems.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>), [Rust](<https://devfeed.tech/topics/rust.md>), [Process](<https://devfeed.tech/topics/process.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [container](<https://devfeed.tech/topics/container.md>), [Server](<https://devfeed.tech/topics/server.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [aws](<https://devfeed.tech/tags/aws.md>), [component](<https://devfeed.tech/tags/component.md>), [errors](<https://devfeed.tech/tags/errors.md>), [http](<https://devfeed.tech/tags/http.md>), [outage](<https://devfeed.tech/tags/outage.md>), [process](<https://devfeed.tech/tags/process.md>), [resilience](<https://devfeed.tech/tags/resilience.md>), [rust](<https://devfeed.tech/tags/rust.md>), [server](<https://devfeed.tech/tags/server.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [servers](<https://devfeed.tech/tags/servers.md>), [systems](<https://devfeed.tech/tags/systems.md>)

### 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

## Formalising external APIs

DevFeed: [Formalising external APIs](<https://devfeed.tech/articles/formalising-external-apis-51504.md>)

Original publisher: [Read original article](<https://gleam.run/news/formalising-external-apis>)

Author: Louis Pilfold

Published: 2025-10-19T00:00:00Z

Content type: release

Language: en

Sources: [Gleam](<https://devfeed.tech/sources/gleam.md>)

Topics: [Tool](<https://devfeed.tech/topics/tool.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [conditionals](<https://devfeed.tech/topics/conditionals.md>), [adapter pattern](<https://devfeed.tech/topics/adapter-pattern.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [code beautification](<https://devfeed.tech/topics/code-beautification.md>), [import](<https://devfeed.tech/topics/import.md>), [modules](<https://devfeed.tech/topics/modules.md>), [Sequences](<https://devfeed.tech/topics/sequences.md>), [Functional programming](<https://devfeed.tech/topics/functional-programming.md>), [identifier](<https://devfeed.tech/topics/identifier.md>), [Exception handling](<https://devfeed.tech/topics/exception-handling.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [beam](<https://devfeed.tech/tags/beam.md>), [data](<https://devfeed.tech/tags/data.md>), [data-types](<https://devfeed.tech/tags/data-types.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [ecosystems](<https://devfeed.tech/tags/ecosystems.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [external](<https://devfeed.tech/tags/external.md>), [interface](<https://devfeed.tech/tags/interface.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [overhead](<https://devfeed.tech/tags/overhead.md>), [performance](<https://devfeed.tech/tags/performance.md>), [wrapper](<https://devfeed.tech/tags/wrapper.md>)

### AI overview

Gleam v1.13.0 adds a documented guide for externals and a dedicated JavaScript API for constructing and inspecting Gleam data. Existing JavaScript externals will need to migrate, with tooling and team help planned. The compiler also prunes redundant bit-array checks and warns about impossible bit patterns, unused recursive arguments, and inefficient list-length emptiness checks. Build output now reports dependency changes to support auditing locked versions. Many language-server improvements add or refine code actions, including extracting functions, expanding and collapsing pattern matches, and generating functions across modules; extraction uses a placeholder name because of an LSP limitation. Other changes improve type names in generated documentation and editor actions, syntax diagnostics, and formatter behavior.

### Source excerpt

Gleam is a type-safe and scalable language for the Erlang virtual machine and JavaScript runtimes. Today Gleam v1.13.0 has been published. Let's go over all the highlights now. External API for Gleam data One of Gleam's strengths is that it is part of the BEAM and JavaScript ecosystems, enabling Gleam programs to take advantage of code written in Erlang, Elixir, JavaScript, and more. This is a large part of how Gleam was able to become a practical production-ready language so quickly, by not restricting Gleam programmers to just the comparatively young Gleam package ecosystem. A function written in one of these other languages can be imported into a Gleam module as an "external function", and then called without any additional performance overhead. @external(erlang, "moon_base", "launch_spaceship") pub fn lift_off(countdown: Int) -> Result(Spaceship, LaunchError) Here the Erlang function launch_spaceship from the module moon_base is being imported. One restriction to external functions is that they will need to return data types that Gleam can understand. Gleam's "external type" feature lets the programmer refer to types defined in other languages, but if the programmer wants to be able to directly construct and pattern match data from external functions it will need to be in a format compatible with Gleam data types. Often a programmer will write a small wrapper function in the external language to convert the data, and also to make the interface adhere to Gleam patterns and conventions. -module(moon_base). -export([launch_spaceship/1]). launch_spaceship(Countdown) -> try Spaceship = launch_control:launch_spaceship(Countdown), {ok, Spaceship} catch error:no_fuel -> {error, no_fuel}; error:bad_weather -> {error, bad_weather} end. This launch_spaceship Erlang function wraps the function from the launch_control module, converting the exception-based API into a Result type, the Erlang representation of Gleam's Ok and Error variants. One thing that a Gleam programmer ma

## No more dependency management headaches

DevFeed: [No more dependency management headaches](<https://devfeed.tech/articles/no-more-dependency-management-headaches-51509.md>)

Original publisher: [Read original article](<https://gleam.run/news/no-more-dependency-management-headaches>)

Author: Louis Pilfold

Published: 2025-08-05T00:00:00Z

Content type: release

Language: en

Sources: [Gleam](<https://devfeed.tech/sources/gleam.md>)

Topics: [Dependency management](<https://devfeed.tech/topics/dependency-management.md>), [Package Management](<https://devfeed.tech/topics/package-management.md>), [Algorithms](<https://devfeed.tech/topics/algorithms.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>)

Tags: [dependency](<https://devfeed.tech/tags/dependency.md>), [dependency-management](<https://devfeed.tech/tags/dependency-management.md>), [error](<https://devfeed.tech/tags/error.md>), [error-messages](<https://devfeed.tech/tags/error-messages.md>), [javascript](<https://devfeed.tech/tags/javascript.md>)

### AI overview

Gleam v1.12.0 makes dependency conflicts easier to resolve by showing the package version requirements that clash, and `gleam update` and `gleam deps download` now report when newer major versions are available. Major upgrades may include breaking changes, so developers still need to check compatibility. Other changes include custom messages for `echo`, smaller generated output, more flexible list formatting, and JSDoc comments in JavaScript output. Compiler diagnostics add hints for discarded variables and redundant comparisons; the release also enables conservative Erlang local-function inlining, which may improve performance for some BEAM programs.

### Source excerpt

Gleam is a type-safe and scalable language for the Erlang virtual machine and JavaScript runtimes. Today Gleam v1.12.0 has been published. Let's take a look at the highlights. Understanding dependency conflicts Gleam packages use semantic versioning, and they specify what ranges of releases they are compatible with to ensure that all selected versions are compatible with each other. This is very useful in ensuring that you don't end up stuck with invalid versions that cause the project to fail to compile, or are broken in more confusing subtle ways. This does, however, mean that sometimes you will have conflicts when adding a dependency, as there's no version which is compatible with the existing versions you have locked. Historically this has been very confusing as we haven't been able to display much useful information when this happens. error: Dependency resolution failed An error occurred while determining what dependency packages and versions should be downloaded. The error from the version resolver library was: Unable to find compatible versions for the version constraints in your gleam.toml. The conflicting packages are: - app - wisp - mist - gleam_otp - gleam_json It's not clear at all what the problem is, or what the programmer might need to do to resolve the problem. This is not fun for them at all. Thanks to a lot of hard work from Jak and a new release of the underlying pubgrub version solving algorithm library Gleam will now provide much clearer error messages: error: Dependency resolution failed There's no compatible version of `gleam_otp`: - You require wisp >= 1.0.0 and < 2.0.0 - wisp requires mist >= 1.2.0 and < 5.0.0 - mist requires gleam_otp >= 0.9.0 and < 1.0.0 - You require lustre >= 5.2.1 and < 6.0.0 - lustre requires gleam_otp >= 1.0.0 and < 2.0.0 There's no compatible version of `gleam_json`: - You require wisp >= 1.0.0 and < 2.0.0 - wisp requires gleam_json >= 3.0.0 and < 4.0.0 - You require gleam_json >= 2.3.0 and < 3.0.0 Version solving is

## A Simple Example of Calling an Elixir Library from Gleam

DevFeed: [A Simple Example of Calling an Elixir Library from Gleam](<https://devfeed.tech/articles/a-simple-example-of-calling-an-elixir-library-from-gleam-52809.md>)

Original publisher: [Read original article](<https://mtlynch.io/notes/gleam-call-elixir/>)

Author: Michael Lynch

Published: 2025-06-08T00:00:00Z

Content type: tutorial

Language: en

Sources: [Mtlynch](<https://devfeed.tech/sources/mtlynch-io.md>)

Topics: [Elixir](<https://devfeed.tech/topics/elixir.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [Library](<https://devfeed.tech/topics/library.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [Nix](<https://devfeed.tech/topics/nix.md>), [CSV](<https://devfeed.tech/topics/csv.md>)

Tags: [beginner](<https://devfeed.tech/tags/beginner.md>), [code](<https://devfeed.tech/tags/code.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [library](<https://devfeed.tech/tags/library.md>), [nix](<https://devfeed.tech/tags/nix.md>)

### AI overview

A beginner-oriented example of calling an Elixir library from a Gleam project. It covers installing Gleam, Erlang, and Elixir dependencies, creating a project, working around a package-version bug, installing a CSV package, and exploring its API with Elixir's interactive shell.

### Source excerpt

I've been experimenting a bit with Gleam and Elixir lately as part of my search for a new programming language. One of Gleam's flagship features is that it can call Elixir code and libraries, but I couldn't find any examples of how to do that. I wrote a simple example of calling an Elixir library from a Gleam project, based on my beginner's understanding of the Gleam/Elixir/Erlang ecosystem. Install dependencies For this example, I'm using

## The fellowship of the forgotten

DevFeed: [The fellowship of the forgotten](<https://devfeed.tech/articles/the-fellowship-of-the-forgotten-35655.md>)

Original publisher: [Read original article](<https://engineering.klarna.com/the-fellowship-of-the-forgotten-d341045a6123?source=rss----86090d14ab52---4>)

Author: Onno Vos Dev

Published: 2025-02-26T09:04:27Z

Content type: article

Language: en

Sources: [Klarna Engineering](<https://devfeed.tech/sources/klarna-engineering.md>)

Topics: [Database](<https://devfeed.tech/topics/database.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [zero downtime deployment](<https://devfeed.tech/topics/zero-downtime-deployment.md>), [consistency](<https://devfeed.tech/topics/consistency.md>), [database-consistency](<https://devfeed.tech/topics/database-consistency.md>), [copy](<https://devfeed.tech/topics/copy.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>)

Tags: [2018](<https://devfeed.tech/tags/2018.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [custom](<https://devfeed.tech/tags/custom.md>), [downtime](<https://devfeed.tech/tags/downtime.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [klarna](<https://devfeed.tech/tags/klarna.md>), [leveldb](<https://devfeed.tech/tags/leveldb.md>), [memory](<https://devfeed.tech/tags/memory.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [replication](<https://devfeed.tech/tags/replication.md>), [serializable](<https://devfeed.tech/tags/serializable.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [source-of-truth](<https://devfeed.tech/tags/source-of-truth.md>)

### AI overview

Klarna migrated KRED from a 15 TB Mnesia cluster to Postgres with no observed downtime, using a staged transition that kept rollback possible. Sharding was set aside because surrounding systems and required components were not ready. Instead, the team preserved KRED's kdb API as a compatibility layer, added record types and null handling for Postgres, and replicated data between Mnesia and Postgres so either could lead. Batching helped Postgres replication keep pace; prepared transactions were chosen for Postgres-to-Mnesia replication because they changed less of the stable Mnesia follower logic, despite adding latency. A live key-level comparison process checked that writes and deletes converged across replicas. After the cutover, logical decoding of transaction-log messages in Postgres WAL replaced prepared transactions, requiring an upgrade to Postgres 14 and a decoder change; this reduced transaction time by about 20 ms. The authors emphasize proof of concept work, small useful steps, and extensive testing and monitoring. The excerpt says isolation-level details are reserved for a second post.

### 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](<https://devfeed.tech/articles/new-chainguard-images-december-2024-adoptium-awx-couchdb-13175.md>)

Original publisher: [Read original article](<https://www.chainguard.dev/unchained/new-chainguard-images-december-2024-adoptium-awx-couchdb>)

Published: 2025-01-16T00:00:00Z

Content type: release

Language: en

Sources: [Chainguard: Unchained](<https://devfeed.tech/sources/chainguard-unchained.md>)

Topics: [Adoptium](<https://devfeed.tech/topics/adoptium.md>), [openjdk](<https://devfeed.tech/topics/openjdk.md>), [Ansible](<https://devfeed.tech/topics/ansible.md>), [Java](<https://devfeed.tech/topics/java.md>), [NoSQL](<https://devfeed.tech/topics/nosql.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [.NET MAUI](<https://devfeed.tech/topics/net-maui.md>), [Process](<https://devfeed.tech/topics/process.md>)

Tags: [adoptium](<https://devfeed.tech/tags/adoptium.md>), [ansible](<https://devfeed.tech/tags/ansible.md>), [apache](<https://devfeed.tech/tags/apache.md>), [awx](<https://devfeed.tech/tags/awx.md>), [chainguard](<https://devfeed.tech/tags/chainguard.md>), [chainguard-images](<https://devfeed.tech/tags/chainguard-images.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [couchdb](<https://devfeed.tech/tags/couchdb.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [helm](<https://devfeed.tech/tags/helm.md>), [java](<https://devfeed.tech/tags/java.md>), [jdk](<https://devfeed.tech/tags/jdk.md>), [linkerd](<https://devfeed.tech/tags/linkerd.md>), [net-11](<https://devfeed.tech/tags/net-11.md>), [nosql](<https://devfeed.tech/tags/nosql.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [opentofu](<https://devfeed.tech/tags/opentofu.md>)

### 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](<https://devfeed.tech/articles/elixir-clustering-using-postgres-365.md>)

Original publisher: [Read original article](<https://supabase.com/blog/elixir-clustering-using-postgres>)

Author: Filipe Cabaço

Published: 2024-01-09T07:00:00Z

Content type: article

Language: en

Sources: [Supabase](<https://devfeed.tech/sources/supabase-blog.md>)

Topics: [Elixir](<https://devfeed.tech/topics/elixir.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [Supabase](<https://devfeed.tech/topics/supabase.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [Latency](<https://devfeed.tech/topics/latency.md>)

Tags: [building](<https://devfeed.tech/tags/building.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [latency](<https://devfeed.tech/tags/latency.md>), [learn](<https://devfeed.tech/tags/learn.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [servers](<https://devfeed.tech/tags/servers.md>)

### 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](<https://devfeed.tech/articles/router-2-0-common-runtime-router-the-road-to-beta-26491.md>)

Original publisher: [Read original article](<https://www.heroku.com/blog/router-2dot0-the-road-to-beta/>)

Author: Elizabeth Cox

Published: 2023-10-30T22:00:00Z

Content type: article

Language: en

Sources: [Heroku](<https://devfeed.tech/sources/heroku.md>)

Topics: [Heroku](<https://devfeed.tech/topics/heroku.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [Server](<https://devfeed.tech/topics/server.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>), [legacy systems](<https://devfeed.tech/topics/legacy-systems.md>), [Scalability](<https://devfeed.tech/topics/scalability.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [concurrency](<https://devfeed.tech/tags/concurrency.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [http-server](<https://devfeed.tech/tags/http-server.md>), [legacy](<https://devfeed.tech/tags/legacy.md>), [modernization](<https://devfeed.tech/tags/modernization.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [release](<https://devfeed.tech/tags/release.md>), [router-2-0](<https://devfeed.tech/tags/router-2-0.md>), [routing](<https://devfeed.tech/tags/routing.md>), [scalability](<https://devfeed.tech/tags/scalability.md>)

### 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.

## Phoenix LiveView latency and rendering optimizations

DevFeed: [Phoenix LiveView latency and rendering optimizations](<https://devfeed.tech/articles/supercharge-your-app-latency-and-rendering-optimizations-in-phoenix-liveview-44007.md>)

Original publisher: [Read original article](<https://dashbit.co/blog/latency-rendering-liveview>)

Author: José Valim

Published: 2023-10-17T00:00:00Z

Content type: article

Language: en

Sources: [Dashbit Blog](<https://devfeed.tech/sources/dashbit-blog.md>)

Topics: [Latency](<https://devfeed.tech/topics/latency.md>), [phoenix](<https://devfeed.tech/topics/phoenix.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [Server-side rendering](<https://devfeed.tech/topics/server-side-rendering.md>), [Optimization](<https://devfeed.tech/topics/optimization.md>), [Framework](<https://devfeed.tech/topics/framework.md>), [Library](<https://devfeed.tech/topics/library.md>)

Tags: [client](<https://devfeed.tech/tags/client.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [latency](<https://devfeed.tech/tags/latency.md>), [liveview](<https://devfeed.tech/tags/liveview.md>), [optimize](<https://devfeed.tech/tags/optimize.md>), [performance](<https://devfeed.tech/tags/performance.md>), [phoenix](<https://devfeed.tech/tags/phoenix.md>), [web](<https://devfeed.tech/tags/web.md>), [websocket](<https://devfeed.tech/tags/websocket.md>)

### AI overview

This article describes how Phoenix LiveView optimizes latency, bandwidth, and client-side rendering through server-rendered HTML, a JavaScript client, and stateful WebSocket connections supported by the Erlang VM.

### Source excerpt

LiveView's unique integration between server and client allows it to drastically optimize both latency and bandwidth, leading to user experiences that are faster and smoother than any other client-server combo out there

## Hopping into spring with Chainguard's RabbitMQ Image

DevFeed: [Hopping into spring with Chainguard's RabbitMQ Image](<https://devfeed.tech/articles/hopping-into-spring-with-chainguard-s-rabbitmq-image-13082.md>)

Original publisher: [Read original article](<https://www.chainguard.dev/unchained/hopping-into-spring-with-chainguards-rabbitmq-image>)

Published: 2023-02-24T00:00:00Z

Content type: article

Language: en

Sources: [Chainguard: Unchained](<https://devfeed.tech/sources/chainguard-unchained.md>)

Topics: [chainguard images](<https://devfeed.tech/topics/chainguard-images.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>), [Security](<https://devfeed.tech/topics/security.md>), [Cloud Native Ecosystem](<https://devfeed.tech/topics/cloud-native-ecosystem.md>), [container](<https://devfeed.tech/topics/container.md>), [vulnerability scanning](<https://devfeed.tech/topics/vulnerability-scanning.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [base-images](<https://devfeed.tech/tags/base-images.md>), [bazel](<https://devfeed.tech/tags/bazel.md>), [chainguard](<https://devfeed.tech/tags/chainguard.md>), [chainguard-images](<https://devfeed.tech/tags/chainguard-images.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [containers](<https://devfeed.tech/tags/containers.md>), [cosign](<https://devfeed.tech/tags/cosign.md>), [cves](<https://devfeed.tech/tags/cves.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [image](<https://devfeed.tech/tags/image.md>), [messaging](<https://devfeed.tech/tags/messaging.md>), [minimal-image](<https://devfeed.tech/tags/minimal-image.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [rabbitmq](<https://devfeed.tech/tags/rabbitmq.md>), [rabbitmq-image](<https://devfeed.tech/tags/rabbitmq-image.md>), [sboms](<https://devfeed.tech/tags/sboms.md>), [secure-images](<https://devfeed.tech/tags/secure-images.md>), [security](<https://devfeed.tech/tags/security.md>), [slsa](<https://devfeed.tech/tags/slsa.md>), [software-supply-chain](<https://devfeed.tech/tags/software-supply-chain.md>)

### 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.

## GitHub Advisory Database now includes Erlang and Elixir advisories

DevFeed: [GitHub Advisory Database now includes Erlang and Elixir advisories](<https://devfeed.tech/articles/github-advisory-database-now-includes-erlang-and-elixir-advisories-73978.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2022-06-27-github-advisory-database-now-includes-erlang-and-elixir-advisories>)

Author: Sidi Merzouk

Published: 2022-06-27T21:28:50Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [GitHub](<https://devfeed.tech/topics/github.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [Elixir](<https://devfeed.tech/topics/elixir.md>)

Tags: [alerts](<https://devfeed.tech/tags/alerts.md>), [composer](<https://devfeed.tech/tags/composer.md>), [dependabot](<https://devfeed.tech/tags/dependabot.md>), [dependency-graph](<https://devfeed.tech/tags/dependency-graph.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [ecosystems](<https://devfeed.tech/tags/ecosystems.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [future](<https://devfeed.tech/tags/future.md>), [github](<https://devfeed.tech/tags/github.md>), [github-advisory-database](<https://devfeed.tech/tags/github-advisory-database.md>), [go](<https://devfeed.tech/tags/go.md>), [hex](<https://devfeed.tech/tags/hex.md>), [maven](<https://devfeed.tech/tags/maven.md>), [npm](<https://devfeed.tech/tags/npm.md>), [nuget](<https://devfeed.tech/tags/nuget.md>), [pip](<https://devfeed.tech/tags/pip.md>), [rubygems](<https://devfeed.tech/tags/rubygems.md>), [security](<https://devfeed.tech/tags/security.md>), [security-advisories](<https://devfeed.tech/tags/security-advisories.md>)

### AI overview

The GitHub Advisory Database now includes curated security advisories for Erlang [Hex] and Elixir, bringing its supported ecosystems to nine. The excerpt says dependency graph support and Dependabot alerts for this ecosystem will be available in the future.

### Source excerpt

The GitHub Advisory Database now includes curated security advisories on Erlang [Hex], Elixir, and more. This brings the Advisory Database to nine supported ecosystems, including: Composer, Go, Maven, npm, NuGet,...

## GitHub Advisory Database now supports Erlang and Elixir packages!

DevFeed: [GitHub Advisory Database now supports Erlang and Elixir packages!](<https://devfeed.tech/articles/github-advisory-database-now-supports-erlang-and-elixir-packages-68285.md>)

Original publisher: [Read original article](<https://github.blog/security/supply-chain-security/github-advisory-database-now-supports-erlang-and-elixir-packages/>)

Author: Madison Ficorilli

Published: 2022-06-27T20:24:52Z

Content type: news

Language: en

Sources: [GitHub Blog](<https://devfeed.tech/sources/github-engineering.md>)

Topics: [Elixir](<https://devfeed.tech/topics/elixir.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [NVD](<https://devfeed.tech/topics/nvd.md>)

Tags: [elixir](<https://devfeed.tech/tags/elixir.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [github](<https://devfeed.tech/tags/github.md>), [github-advisory-database](<https://devfeed.tech/tags/github-advisory-database.md>), [security](<https://devfeed.tech/tags/security.md>), [supply-chain-security](<https://devfeed.tech/tags/supply-chain-security.md>)

### AI overview

GitHub's Advisory Database has added curated security advisories for Erlang, Elixir, and other packages in the Hex ecosystem. The open source database offers vulnerability information and accepts community contributions for supported Hex packages.

### Source excerpt

We're excited to announce that the GitHub Advisory Database now includes curated security advisories on Erlang, Elixir, and more.

## Announcing Livebook

DevFeed: [Announcing Livebook](<https://devfeed.tech/articles/announcing-livebook-43982.md>)

Original publisher: [Read original article](<https://dashbit.co/blog/announcing-livebook>)

Author: José Valim

Published: 2021-04-13T00:00:00Z

Content type: release

Language: en

Sources: [Dashbit Blog](<https://devfeed.tech/sources/dashbit-blog.md>)

Topics: [Web app](<https://devfeed.tech/topics/webapp.md>), [Code](<https://devfeed.tech/topics/code.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Elixir](<https://devfeed.tech/topics/elixir.md>), [phoenix](<https://devfeed.tech/topics/phoenix.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [Deep neural networks](<https://devfeed.tech/topics/deep-neural-networks.md>)

Tags: [application](<https://devfeed.tech/tags/application.md>), [axon](<https://devfeed.tech/tags/axon.md>), [code](<https://devfeed.tech/tags/code.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [computing](<https://devfeed.tech/tags/computing.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [exla](<https://devfeed.tech/tags/exla.md>), [interactive](<https://devfeed.tech/tags/interactive.md>), [library](<https://devfeed.tech/tags/library.md>), [livebook](<https://devfeed.tech/tags/livebook.md>), [liveview](<https://devfeed.tech/tags/liveview.md>), [markdown](<https://devfeed.tech/tags/markdown.md>), [networks](<https://devfeed.tech/tags/networks.md>), [nx](<https://devfeed.tech/tags/nx.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [phoenix](<https://devfeed.tech/tags/phoenix.md>), [tool](<https://devfeed.tech/tags/tool.md>), [users](<https://devfeed.tech/tags/users.md>), [using](<https://devfeed.tech/tags/using.md>), [web](<https://devfeed.tech/tags/web.md>), [writing](<https://devfeed.tech/tags/writing.md>)

### AI overview

Dashbit announces Livebook, an open-source web application for interactive and collaborative Elixir notebooks built with Phoenix LiveView. It supports Markdown and Elixir cells, sequential evaluation, persistence, custom runtimes, explicit dependencies, and collaboration across single-node or multi-node deployments.

### Source excerpt

Livebook is a web application for writing interactive and collaborative code notebooks

## 10 years(-ish) of Elixir

DevFeed: [10 years(-ish) of Elixir](<https://devfeed.tech/articles/10-years-ish-of-elixir-44023.md>)

Original publisher: [Read original article](<https://dashbit.co/blog/ten-years-ish-of-elixir>)

Author: José Valim

Published: 2021-01-11T00:00:00Z

Content type: article

Language: en

Sources: [Dashbit Blog](<https://devfeed.tech/sources/dashbit-blog.md>)

Topics: [Elixir](<https://devfeed.tech/topics/elixir.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [Functional programming](<https://devfeed.tech/topics/functional-programming.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [distributed-systems](<https://devfeed.tech/topics/distributed-systems.md>), [Web app](<https://devfeed.tech/topics/webapp.md>)

Tags: [broadway](<https://devfeed.tech/tags/broadway.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [functional-programming](<https://devfeed.tech/tags/functional-programming.md>), [liveview](<https://devfeed.tech/tags/liveview.md>), [membrane](<https://devfeed.tech/tags/membrane.md>), [nerves](<https://devfeed.tech/tags/nerves.md>), [phoenix](<https://devfeed.tech/tags/phoenix.md>), [programming](<https://devfeed.tech/tags/programming.md>), [tooling](<https://devfeed.tech/tags/tooling.md>), [web-applications](<https://devfeed.tech/tags/web-applications.md>)

### AI overview

A retrospective on roughly ten years of Elixir, covering the language's goals, its relationship with Erlang, its focus on extensibility and developer productivity, and examples of companies using it in production.

### Source excerpt

We are celebrating 10 years since the first commit to what would become Elixir.

## How to debug Elixir/Erlang compiler performance

DevFeed: [How to debug Elixir/Erlang compiler performance](<https://devfeed.tech/articles/how-to-debug-elixir-erlang-compiler-performance-44002.md>)

Original publisher: [Read original article](<https://dashbit.co/blog/how-to-debug-elixir-erlang-compiler-performance>)

Author: José Valim

Published: 2020-12-15T00:00:00Z

Content type: tutorial

Language: en

Sources: [Dashbit Blog](<https://devfeed.tech/sources/dashbit-blog.md>)

Topics: [Compiler](<https://devfeed.tech/topics/compiler.md>), [Elixir](<https://devfeed.tech/topics/elixir.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [debugging](<https://devfeed.tech/topics/debugging.md>), [Code](<https://devfeed.tech/topics/code.md>), [Parallelism](<https://devfeed.tech/topics/parallelism.md>), [function](<https://devfeed.tech/topics/function.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [debug](<https://devfeed.tech/tags/debug.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [parallel](<https://devfeed.tech/tags/parallel.md>), [performance](<https://devfeed.tech/tags/performance.md>), [techniques](<https://devfeed.tech/tags/techniques.md>)

### AI overview

A practical guide to diagnosing slow Elixir and Erlang compilation. It explains how to isolate slow files, distinguish compilation and waiting times, identify root causes, and profile compilation stages using compiler timing reports.

### Source excerpt

Explore techniques to debug and improve performance of Erlang/Elixir compiler

[Next page](<https://devfeed.tech/topics/erlang.md?cursor=WyIyMDIwLTEyLTE1VDAwOjAwOjAwKzAwOjAwIiwgImVmMThhOWIyLTc1NzUtNDVjNi1iN2ZlLWQzOTFlMjU0Y2U3MCJd>)