# asynchronous Published articles for asynchronous. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## \[$\] Thread-identity switcheroo for io\_uring DevFeed: [\[$\] Thread-identity switcheroo for io\_uring]() Original publisher: [Read original article]() Author: corbet Published: 2026-09-17T13:49:59Z Content type: article Language: en Sources: [LWN.net]() Topics: [io\_uring](), [execution](), [Kernel]() Tags: [asynchronous](), [execution](), [io-uring](), [kernel](), [performance](), [rfc](), [thread]() ### AI overview An RFC patch set proposes a new approach to preserving io_uring's guarantee that applications do not block during asynchronous execution. The proposal addresses kernel paths not designed for asynchronous execution and the performance cost of existing workarounds. ### Source excerpt The io_uring subsystem is all about asynchronous execution; applications count on it to not block -- unless explicitly requested to. Within io_uring, maintaining the "never blocks" guarantee has sometimes been a challenge, given that many paths in the kernel were never designed for asynchronous execution. This problem has been worked around, but at a significant cost to performance. Now, io_uring maintainer Jens Axboe has posted an RFC patch set with a somewhat radical (and potentially scary) solution to the problem. ## CodeSOD: Asynchronous Directories DevFeed: [CodeSOD: Asynchronous Directories]() Original publisher: [Read original article]() Author: Remy Porter Published: 2026-09-09T06:30:00Z Content type: article Language: en Sources: [The Daily WTF]() Topics: [Vala](), [async/await](), [Library](), [Programming]() Tags: [async](), [asynchronous](), [await](), [codesod](), [exceptions](), [filesystem](), [writing-code]() ### AI overview This article examines implementing an asynchronous version of Vala's directory-creation method when the core library provides only a synchronous version. The proposed function walks up the directory tree, then creates missing directories in reverse order, using exceptions for control flow. ### Source excerpt Eri has a mix of a "true confession" and a "wait, really?" today. The programming language Vala bills itself as a C# like language that compiles into something pretty close to C performance, designed specifically for writing code against Gnome and its associated libraries. One of the C#-isms in brings in is async/await type semantics. You can yield someAsyncFunction(), which returns control to the caller, allowing it to proceed until the yielded function returns an actual value. Because it has asynchronous functions, many library functions for handling I/O are already async. So you can make_directory_async, which yields control so you can keep executing while waiting for the filesystem to make your directory. There are also synchronous versions of those methods. And then there's create_directory_with_parents, which will create a chain of directories for you. That's the synchronous version, and Vala's core library has decided not to provide an asynchronous version of it, which is my "wait, really?" I suspect it's really about the race conditions involved and the risks of things going wrong while doing it asynchronously; all solvable problems, but tricky ones to solve. But it's the problem Eri had, and this is their solution: /// Note: does not throw if target already exists async void create_directory_with_parents_async(File file, Cancellable? cancellable = null) throws Error { var to_create = new File[0]; var? current_target = file; while(current_target != null) { try { yield current_target.make_directory_async(Priority.DEFAULT, cancellable); } catch(IOError.NOT_FOUND e) { to_create += current_target; current_target = current_target.get_parent(); continue; } catch(IOError.EXISTS e) { break; } break; } for (int i = to_create.length - 1; i >= 0; --i) { try { yield to_create[i].make_directory_async(Priority.DEFAULT, cancellable); } catch(IOError.EXISTS e) { // Created by another process } } } If I'm reading this correctly, we start by trying to create the full path to ## Fill an SMS Verification Code Without Reading the Inbox DevFeed: [Fill an SMS Verification Code Without Reading the Inbox]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-09-07T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [Android](), [iOS](), [Web](), [Security](), [API](), [Accessibility]() Tags: [accessibility](), [android](), [api](), [asynchronous](), [ios](), [otp](), [permission](), [security]() ### AI overview Codename One adds one-time-code autofill, a country-aware phone-number field, and a verification component for iOS, Android, and the browser without requesting access to the rest of the SMS inbox. The article explains the asynchronous verification flow, server-side security responsibilities, and a single-editor design that improves typing, pasting, accessibility, and autofill. ### Source excerpt Codename One adds phone-number and OTP components plus one-time-code autofill on iOS, Android, and the web without requesting permission to read SMS messages. ## Handling Asynchronous Images in Android Screenshot Tests DevFeed: [Handling Asynchronous Images in Android Screenshot Tests]() Original publisher: [Read original article]() Author: Alex Zhukovich Published: 2026-08-27T07:41:23Z Content type: tutorial Language: en Sources: [Alex Zhuk - Android development and testing]() Topics: [Testing](), [Android](), [test](), [Compose]() Tags: [android](), [asynchronous](), [junit](), [screenshot-testing](), [tests]() ### AI overview This tutorial explains why asynchronous image loading makes Android screenshot tests unstable or inconsistent. It presents two approaches for deterministic results: injecting fake images with the coil-test library and using Compose inspection mode when the first approach is unavailable. ### Source excerpt This article is based on a chapter from my book, Mastering Android Screenshot Testing. Modern applications frequently load images asynchronously, which is a common cause of unstable screenshot tests or confusion when you review newly generated screenshots. A test can pass locally and fail on CI, produce a different image ## Native Async/Coroutine Reads in RocksDB DevFeed: [Native Async/Coroutine Reads in RocksDB]() Original publisher: [Read original article]() Author: Josh Kang Published: 2026-08-24T00:00:00Z Content type: release Language: en Sources: [RocksDB]() Topics: [rocksdb](), [Coroutines](), [C++](), [IO](), [API]() Tags: [async](), [asynchronous](), [blog](), [c-plus-plus](), [coroutine](), [io](), [native](), [rocksdb](), [thread]() ### AI overview RocksDB introduces experimental asynchronous Get and MultiGet APIs backed by native C++ coroutines. The APIs can suspend storage-bound reads, allowing a small executor to run other ready tasks and maintain more storage queue depth without one blocked application thread per read. The feature targets throughput for I/O-bound point lookups rather than reducing individual device-read latency. ### Source excerpt A point lookup that misses RocksDB's block cache can spend most of its time waiting for storage. The traditional way to keep more reads in flight is to add threads. That works, but each outstanding read parks a thread, carries a stack, and adds context-switching overhead. RocksDB now has experimental asynchronous Get and MultiGet APIs backed by native C++ coroutines. When a read reaches storage, RocksDB can suspend the request, let its read-executor worker run another ready task, and resume the request when the filesystem reports completion. A small executor can therefore maintain more storage queue depth without requiring one blocked application thread per read. These APIs are available in RocksDB 11.10.0. This is primarily a throughput feature for I/O-bound point lookups. It does not make an individual device read faster. Its benefit comes from keeping the device busy and using CPU threads for runnable work. The API surface RocksDB exposes the new read path through two public interfaces: DB::GetAsync and DB::MultiGetAsync return immediately on the native path and report completion through AsyncCallback::OnComplete. CoroDB::CoGet and CoroDB::CoMultiGet return lazy folly::coro::Task objects. CoGet produces a Status; CoMultiGet fills the same per-key values and statuses as synchronous MultiGet. The callback APIs suit applications that do not expose Folly tasks at their boundaries. The CoroDB APIs let coroutine-based callers await RocksDB directly, avoiding an application-side callback-to-Baton adapter and its extra completion handoff. Native execution requires RocksDB to be built with Folly and USE_COROUTINES=1. Neither interface requires ReadOptions::async_io. That flag continues to control the older internal async-I/O optimizations for synchronous MultiGet and iterators. The task APIs are lazy: no read begins until a task is awaited or started. Both interfaces take pointer and reference parameters, so keep the DB, column-family handles, ReadOptions, keys and their ## Watch Apps: One Codebase, Two Real Applications DevFeed: [Watch Apps: One Codebase, Two Real Applications]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-08-22T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [SwiftUI](), [Android](), [media3](), [SQLite](), [API]() Tags: [android](), [api](), [apk](), [apple](), [apple-watch](), [asynchronous](), [files](), [release](), [sqlite](), [state](), [swiftui](), [watchos]() ### AI overview Codename One can build Apple Watch companion applications and Wear OS applications from a shared watch entry point. The article explains separate application runtimes and storage, platform-specific rendering, and asynchronous communication for live messages, replicated state, and file transfers. ### Source excerpt Codename One now builds Apple Watch companions and standalone Wear OS products from one watch entry point, with a portable asynchronous API for messages, state, and files. ## A Repeatable Human-in-the-Loop Process for Large-Scale LLM Classification DevFeed: [A Repeatable Human-in-the-Loop Process for Large-Scale LLM Classification]() Original publisher: [Read original article]() Author: Anish Kumar Published: 2026-07-11T00:00:00Z Content type: article Language: en Sources: [Scribd Tech]() Topics: [Large Language Model](), [Prompt Engineering](), [Inference](), [datasets](), [data]() Tags: [asynchronous](), [batch](), [content-trust-series](), [cost](), [data](), [databricks](), [datasets](), [evaluation](), [featured](), [inference](), [llm](), [machinelearning](), [models](), [production](), [prompt](), [scribd](), [workflow]() ### AI overview The article presents a repeatable human-in-the-loop process for large-scale LLM classification. It combines fast-model labeling, judge-model disagreement detection, targeted SME review, a golden dataset built from corrections, and selective prompt iteration. ### Source excerpt LLM models change. Prompt quality changes. Cost changes. We assumed that from day one. ## How DeveloperHub Migrated Its Editor and Document Storage Without Downtime DevFeed: [How DeveloperHub Migrated Its Editor and Document Storage Without Downtime]() Original publisher: [Read original article]() Author: Zaid Daba'een Published: 2026-07-05T15:59:20Z Content type: article Language: en Sources: [DeveloperHub.io]() Topics: [migration](), [Documentation](), [Angular](), [Markdown](), [Open Source]() Tags: [angular](), [asynchronous](), [documentation](), [engineering](), [maintenance](), [markdown](), [migration]() ### AI overview DeveloperHub describes replacing its editor, storage format, link model, and history system. The migration moved millions of documents from a text-and-plugins format to a structured document model, ran both systems in parallel, used asynchronous workers, and gated rollout with feature flags so customers experienced no maintenance window or required action. ### Source excerpt How we replaced the heart of DeveloperHub, the editor and the way every page is stored, with zero downtime and nothing for our customers to do ## Community Comebacks, Angular 21.1 Features, and Smarter Signal Forms ⚡ DevFeed: [Community Comebacks, Angular 21.1 Features, and Smarter Signal Forms ⚡]() Original publisher: [Read original article]() Author: Angular Published: 2026-06-19T10:01:04Z Content type: article Language: en Sources: [Angular]() Topics: [Angular](), [Forms](), [async](), [Open Source](), [legacy](), [migration]() Tags: [angular](), [angular-newsletter](), [angular-release](), [angular-weekly](), [async](), [asynchronous](), [forms](), [legacy](), [migration](), [open-source]() ### AI overview This Angular community roundup covers podcast episodes about Angular 20 and developer career setbacks, a recap of Angular 21.1, Signal Forms techniques for asynchronous validators and debouncing, dynamic form lists, an interview about joining the Angular team, and migration to modern Control Flow syntax. ### Source excerpt The Angular community is about much more than just code -- it's about the people building it, their career journeys, and how we collaborate. This week's roundup features inspiring community stories alongside technical deep dives into the Angular 21.1 features and advanced form tuning. Tune into this week's excellent community resources The Dev Life Podcast: Inside Angular 20 & Navigating Layoffs Brooke Avery @JediBravery and Matthew Christiansen back-to-back drop two must-listen episodes of The Dev Life podcast. First, they sit down with Minko Gechev @mgechev to go inside the engineering decisions of Angular 20. Then, they host GDE Chris Perko for an incredibly timely, candid conversation about bouncing back from tech layoffs and turning career setbacks into massive opportunities. Listen to Ep. 3 (Inside Angular 20): https://www.youtube.com/watch?v=QhfXXXzOD6g Listen to Ep. 4 (Navigating Layoffs): https://www.youtube.com/watch?v=laYzvyEDtw8 What was new in Angular 21.1? Alain Chautard @AlainChautard provides a fantastic, concise recap of the January Angular release. If you want to know what minor features, bug fixes, and performance polishes landed in Angular 21.1, this is your go-to guide. Read the release recap: https://blog.angulartraining.com/whats-new-in-angular-21-1-7454f699104f Stop Wasting API Calls! Async Validators & Debouncing Fanis Prodromou @prodromouf tackles a massive real-world performance issue in form handling. Learn how to combine asynchronous validators with debouncing in the Signal Forms API to keep your backend from being overwhelmed by unnecessary API requests. Watch the tutorial: https://youtu.be/R10dQ4zlWs0 Dynamic Lists & Joining the Angular Team (French) Modeste Assiongbon @rblmdst shares two incredible French-language videos this week. Dive into a technical walkthrough on handling dynamic field lists using Signal Forms. Then, catch an inspiring interview with Matthieu Riegler @Jean_Meche, tracking his journey from a casual open-source cont ## Building the Crossplay Board DevFeed: [Building the Crossplay Board]() Original publisher: [Read original article]() Author: The NYT Open Team Published: 2026-06-08T16:46:30Z Content type: tutorial Language: en Sources: [New York Times]() Topics: [Android](), [Development](), [Jetpack Compose](), [Mobile](), [ui](), [screen](), [real-time]() Tags: [android](), [android-app-development](), [asynchronous](), [code](), [compose](), [development](), [draggable](), [jetpack-compose](), [kotlin](), [mobile](), [multiplayer](), [real-time](), [screen]() ### AI overview The New York Times Games team describes building the Android game board for Crossplay, a multiplayer word game with a 15x15 grid, draggable tiles, real-time animation, and asynchronous matches. The team used a hybrid architecture: an Android GridLayout with 225 tile Views integrated into surrounding Jetpack Compose UI. ### Source excerpt How We Made a 15X15 Game Surface Feel at Home on AndriodIllustration by Lehel Kovács By Shafik Quoraishee What Is Crossplay? The New York Times Games team has been building daily puzzles for quite a while: Wordle, Spelling Bee, Connections, The Mini. These are solo games. The player opens them, solves them, and then closes them. This leads to a simple, satisfying experience which delights millions of players a day. Crossplay is an altogether different endeavor. It's the first multiplayer game from NYT Games, and it brings a friend (or a stranger) into the experience with them. So two players, one board, in real time. In Crossplay, players take turns placing letter tiles on a 15x15 grid to form interlocking words, but built for mobile with a focus on speed, fairness, and the back-and-forth tension that compels the player to play one more round. The matches are asynchronous by default. The player makes their move, the opponent gets notified and responds when they're ready. But the board animates as if the players are both sitting at the same table. When we set out to build it, we knew the board would be the hardest part. While the networking, the opponent matching, and the game logic were all challenging work, the board itself which is part of the core game loop was the most difficult piece because of the number of interactions required to make it function correctly, in concert. Since every cell is a potential drop target and every tile is draggable, the board needs to respond instantly to touch *and* animate their opponent's moves *as they happen*. This all must occur on a screen that is a few inches wide. In this post we discuss what it took to get that right on Android. Starting with the Grid One of our first questions was architectural. How should 225 tiles be laid out? Jetpack Compose is the obvious modern choice. But Crossplay's development started before our team had fully migrated to Compose, and the game board had specific requirements that made a pure-Compos ## Xen on RISC-V: Dom0 Boot, Hypercalls and Docker Toolchain DevFeed: [Xen on RISC-V: Dom0 Boot, Hypercalls and Docker Toolchain]() Original publisher: [Read original article]() Author: Baptiste Le Duc Published: 2026-05-22T08:30:21Z Content type: article Language: en Sources: [XCP-ng Blog]() Topics: [RISC-V](), [Docker](), [Tooling](), [Command-line interface]() Tags: [asynchronous](), [boot](), [command-line](), [communication](), [docker](), [interrupt](), [memory](), [risc-v](), [tooling]() ### AI overview This first post in a series reports progress on bringing Xen guest-domain support to RISC-V. It describes Dom0 boot work, hypercall communication through SBI ecall, event-channel notifications, and a Docker environment for building and running the stack on an x86 laptop. ### Source excerpt Latest progress on Xen for RISC-V, including Dom0 boot, hypercalls and Docker-based tooling. ## Orchestrate temporary rate limit increases on Temporal Cloud namespaces DevFeed: [Orchestrate temporary rate limit increases on Temporal Cloud namespaces]() Original publisher: [Read original article]() Author: Taylor Khan Published: 2026-05-19T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Cloud](), [Provisioning]() Tags: [applications](), [asynchronous](), [automatically](), [capacity](), [client](), [cloud](), [how-to](), [provisioning](), [temporal-concepts](), [ttl](), [workflows]() ### AI overview This tutorial presents a Temporal Workflow pattern for temporarily increasing rate limits on Temporal Cloud namespaces during predictable or temporary throughput spikes. A parent Workflow raises the capacity limit, starts an asynchronous Child Workflow, and completes to unblock the client; the Child Workflow waits for a designated duration before restoring the original limit. ### Source excerpt Stop overpaying for peak capacity. Use Temporal Workflows to grant time-bound rate limit increases that revert automatically after the TTL expires. ## Event-Driven Architecture with Apache Kafka DevFeed: [Event-Driven Architecture with Apache Kafka]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-03-16T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [event driven](), [Kafka](), [Apache-Kafka](), [Scalability](), [Resilience](), [streaming-data-processing](), [Latency](), [systems]() Tags: [apache-kafka](), [architecture](), [asynchronous](), [consumer](), [distributed-systems](), [event-driven-architecture](), [event-sourcing](), [kafka](), [microservices](), [partitions](), [real-time](), [resilience](), [scalability](), [schemas](), [stream-processing]() ### AI overview This tutorial explains event-driven architecture and how Apache Kafka supports asynchronous, real-time data processing. It covers producers, consumers, immutable events, event sourcing, scalability, resilience, stream-processing pipelines, and challenges such as ordering, debugging, and eventual consistency. ### Source excerpt Event-driven architecture replaces synchronous point-to-point calls with immutable events on a durable log, so producers and consumers scale and fail independently. Kafka provides that log: topics sharded into ordered append-only partitions, replicated across brokers, with consumer groups sharing partitions to scale read throughput. ## How io\_uring improves database performance DevFeed: [How io\_uring improves database performance]() Original publisher: [Read original article]() Published: 2025-12-11T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's Blog]() Topics: [io\_uring](), [Databases](), [Linux Kernel](), [NVMe]() Tags: [asynchronous](), [database-performance](), [io](), [io-uring](), [nvme](), [performance]() ### AI overview This article explains how io_uring improves database performance through shared submission and completion queues, batching, fewer system calls, zero-copy operation, and features such as SQPoll and registered buffers. It also discusses DMA and the relevance of fast NVMe storage. ### Source excerpt . [How io_uring Improves Database Performance](how-iouring-improves-database-performance-cover... ## Engineering at Deliveroo India: How We Build, Collaborate, and Grow DevFeed: [Engineering at Deliveroo India: How We Build, Collaborate, and Grow]() Original publisher: [Read original article]() Author: Kartik Visvanathan Published: 2025-11-06T00:00:00Z Content type: article Language: en Sources: [Deliveroo]() Topics: [Development](), [idc](), [Slack](), [Figma](), [systems]() Tags: [asynchronous](), [collaboration](), [cross-functional-teams](), [development](), [engineering](), [figma](), [india](), [slack]() ### AI overview Kartik Visvanathan describes how Deliveroo's India engineering hub operates as a global, cross-functional development center. The article covers team ownership, collaboration across time zones, co-located roles, asynchronous communication, and tools including Slack, Confluence, and Figma. ### Source excerpt Hey everyone, I'm Kartik Visvanathan, an Engineering Manager at Deliveroo, based in India. I joined the team in 2023, and it's been an exciting ride ever since. I've built some truly impactful products here, including an advertising platform that we scaled into a profitable business, and a corporate orders product that touched every part of our systems--from restaurants to delivery to customer service. But while building cool stuff is awesome, what I really want to share today is the secret sauce behind it: how we work as a team here in India. A Truly Global Hub Our engineering hub in India is a core driver of Deliveroo's global mission. Over the past few years, our teams have transitioned and taken complete ownership of key product areas. Whether we're improving the restaurant onboarding flow or fine-tuning our delivery times, the work we do here is absolutely core to Deliveroo's success. When our India Development Center (IDC) started a few years back, we had engineers reporting directly to managers in the UK. I was one of the first engineering managers hired in India in 2023, and I was given the opportunity to build a team that was entirely based here. We've since grown to include other roles like product managers, analytics engineers, and data scientists right here in India. This lets us have "co-located teams"--people who can sit in the same room, grab a whiteboard, and even go out for a team social that isn't virtual. When candidates ask about my favorite parts of the job, I always mention three things: cross-team collaboration, work flexibility and life harmony, and a culture of ownership. So let's dive into those. How We Collaborate Across Teams Working with teammates in London and other time zones means a lot of asynchronous communication. We rely heavily on tools like Slack, Confluence, and Figma, which are essentially our digital whiteboards. Regular virtual stand-ups and a focus on clear ownership help us build trust and keep things moving. In the advertis ## Temporal Ruby SDK Reaches General Availability with Rust Core and Deterministic Fiber Scheduler DevFeed: [Temporal Ruby SDK Reaches General Availability with Rust Core and Deterministic Fiber Scheduler]() Original publisher: [Read original article]() Author: Chad Retz Published: 2025-10-16T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Ruby](), [SDKs](), [Rust](), [Programming](), [cancellation](), [Code](), [Open Source]() Tags: [announcements](), [asynchronous](), [cancellation](), [fiber](), [guardrails](), [open-source](), [ruby](), [rust](), [scheduler](), [sdk](), [workflows]() ### AI overview Temporal Ruby is now generally available, providing Ruby developers with a native-feeling SDK for building durable software and Workflows. The article introduces its programming model and demonstrates Activities, deterministic fibers, durable timers, cancellation, and updates, while also discussing the Rust-powered implementation and execution guardrails. ### Source excerpt Temporal Ruby SDK is GA. Build durable Ruby Workflows with native APIs, a Rust-powered core, a deterministic fiber scheduler, and guardrails for safe execution. ## Kotlin Coroutines Compared with Reactor for Sequential and Asynchronous Operations DevFeed: [Kotlin Coroutines Compared with Reactor for Sequential and Asynchronous Operations]() Original publisher: [Read original article]() Published: 2025-10-06T00:00:00Z Content type: comparison Language: en Sources: [Kt. Academy]() Topics: [Coroutines](), [Kotlin](), [kotlin-coroutines](), [Reactive Streams](), [RxJava](), [async/await](), [Android](), [Back end]() Tags: [android](), [async](), [asynchronous](), [await](), [backend](), [compare](), [comparison](), [coroutines](), [kotlin](), [kotlin-coroutines](), [programming](), [programming-languages](), [reactive-streams](), [rxjava](), [simple](), [time](), [workshop-learning-programming]() ### AI overview This article compares Kotlin Coroutines with Reactor for backend and Android development. It argues that coroutines provide more readable and straightforward syntax for sequential and asynchronous operations, while Reactor requires additional operators, concepts, and patterns. ### Source excerpt A comparison of Kotlin Coroutines and Reactor, highlighting the elegance and simplicity of Coroutines over the complexity of Reactor. ## Kotlin Coroutines and JavaScript DevFeed: [Kotlin Coroutines and JavaScript]() Original publisher: [Read original article]() Published: 2025-09-08T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [JavaScript](), [Kotlin](), [kotlin-coroutines](), [Concurrency](), [Promise](), [TypeScript](), [React]() Tags: [async](), [asynchronous](), [callback](), [coroutines](), [how-to](), [javascript](), [kotlin](), [kotlin-coroutines](), [react](), [typescript](), [workshop-learning-programming]() ### AI overview This tutorial explains how to make Kotlin Coroutines APIs usable from JavaScript and TypeScript projects. It covers converting suspending functions to JavaScript async functions, exposing Flow values through callbacks or wrapper classes, and calling regular or promise-returning JavaScript functions from Kotlin Coroutines. ### Source excerpt How to use Kotlin Coroutines in JavaScript projects, or JavaScript libraries from Kotlin Coroutines. ## Converting Future to CompletableFuture With Java Virtual Threads DevFeed: [Converting Future to CompletableFuture With Java Virtual Threads]() Original publisher: [Read original article]() Published: 2025-07-17T08:25:00Z Content type: tutorial Language: en Sources: [Gunnar Morling]() Topics: [Java](), [Concurrency](), [Concurrent Programming]() Tags: [api](), [asynchronous](), [blocking](), [java](), [java-8](), [threads]() ### AI overview This tutorial explains how Java 21+ virtual threads can help convert legacy Future objects into CompletableFuture instances. It contrasts blocking, polling, and asynchronous approaches, noting that virtual threads make blocking inexpensive by unmounting blocked threads from their underlying platform threads. ### Source excerpt This post explores how virtual threads in Java 21+ provide an elegant solution for converting legacy Future objects into CompletableFuture instances. Since Java 8, the CompletableFuture API provides a convenient way for performing asynchronous operations in a functional, composable way. This makes it very simple to call some long-running methods--for instance involving external I/O--asynchronously and process each result as soon as it is available, without blocking on any threads: ## Understanding Futures and await in Dart and Flutter DevFeed: [Understanding Futures and await in Dart and Flutter]() Original publisher: [Read original article]() Author: Marvin März Published: 2025-05-27T08:28:16Z Content type: tutorial Language: en Sources: [QuickBird Studios Blog]() Topics: [Dart](), [Flutter](), [event driven](), [Concurrency]() Tags: [asynchronous](), [await](), [concurrency](), [dart](), [event-driven](), [flutter](), [future](), [post]() ### AI overview This tutorial explains how Futures and await work in Dart and Flutter, including their interaction with Dart's single-threaded event loop, asynchronous I/O, and common pitfalls. ### Source excerpt Futures in Dart might seem straightforward at first glance, but dig a little deeper, and you'll find they can be more intricate than you initially thought. Ever wondered how these asynchronous operations truly play with Dart's single-threaded event loop? Or perhaps you've stumbled upon some of the common pitfalls that can trip up even experienced Flutter developers? Fear not, because we're about to embark on a journey to unravel the mysteries of Futures in Dart and Flutter. The post Why Await? Futures in Dart & Flutter appeared first on QuickBird Studios. ## Postgres 18 Beta 1 Introduces Asynchronous I/O and Upgrade and Observability Changes DevFeed: [Postgres 18 Beta 1 Introduces Asynchronous I/O and Upgrade and Observability Changes]() Original publisher: [Read original article]() Author: Heikki Linnakangas Published: 2025-05-08T21:17:13Z Content type: release Language: en Sources: [Blog -- Neon Docs]() Topics: [releases](), [Release notes](), [io\_uring](), [observability](), [Linux](), [Statistics]() Tags: [asynchronous](), [io-uring](), [linux](), [observability](), [performance](), [postgres](), [release](), [release-notes](), [statistics]() ### AI overview Neon contributors describe the Postgres 18 Beta 1 release, highlighting its new asynchronous I/O subsystem, selectable I/O methods including io_uring, retained planner statistics during pg_upgrade, new upgrade options, and observability changes. ### Source excerpt Postgres 18 Beta 1 just shipped. As with previous major releases, this beta includes previews of all features planned for general availability. Read the release notes for the full list of updates, but we're gonna go through some highlights on this post. New in Postgres 18 Asynchr... ## Announcing Lix 2.93 "Bici Bici" DevFeed: [Announcing Lix 2.93 "Bici Bici"]() Original publisher: [Read original article]() Published: 2025-05-06T00:00:00Z Content type: release Language: en Sources: [News on Lix]() Topics: [releases](), [Release notes](), [Nix](), [upgrade](), [deprecated](), [configuration]() Tags: [announce](), [asynchronous](), [bugfixes](), [configuration](), [deprecated](), [release](), [upgrade](), [version]() ### AI overview The Lix team announces version 2.93, a major release focused on bug fixes and continued integration with the KJ asynchronous runtime. The release also deprecates CR/CRLF line endings and literal NUL bytes in Nix expressions, which produce errors by default. ### Source excerpt We at the Lix team are proud to announce our fourth major release, version 2.93 "Bici Bici". This release focuses on bugfixes and continues integrating Lix with the KJ asynchronous runtime, in order to replace the previous bespoke implementation. ## The Synchrony Budget DevFeed: [The Synchrony Budget]() Original publisher: [Read original article]() Published: 2025-03-18T13:00:00Z Content type: article Language: en Sources: [Gunnar Morling]() Topics: [Network](), [Availability](), [Kafka]() Tags: [asynchronous](), [availability](), [distributed](), [e-commerce](), [kafka](), [network](), [services]() ### AI overview The article introduces the "synchrony budget," a design principle for distributed services: minimize synchronous calls to reduce request latency and dependencies that can lower service availability. It uses an e-commerce order flow to argue that shipment notifications can be handled asynchronously, such as through a Kafka topic, when an immediate response is unnecessary. ### Source excerpt For building a system of distributed services, one concept I think is very valuable to keep in mind is what I call the synchrony budget: as much as possible, a service should minimize the number of synchronous requests which it makes to other services. ## Queueing Without a Queue: The PostgreSQL Hack DevFeed: [Queueing Without a Queue: The PostgreSQL Hack]() Original publisher: [Read original article]() Author: Puppo92 Published: 2025-03-13T10:38:36Z Content type: tutorial Language: en Sources: [Backend Job: skill, salary and insights - Codemotion Magazine]() Topics: [PostgreSQL](), [Database](), [Node.js](), [npm](), [Library]() Tags: [api](), [asynchronous](), [backend](), [code](), [docker](), [git](), [implementation](), [installation](), [javascript](), [library](), [node](), [node-js](), [npm](), [postgresql](), [queue](), [schema](), [typescript]() ### AI overview A tutorial on implementing queueing with pg-boss, an NPM library that provides background processing and reliable asynchronous execution for Node.js applications using PostgreSQL for queue storage and management. ### Source excerpt This second article about queueing without a queue focuses on implementation based on PostgreSQL. This solution moves the queue implementation from the node system to the database, where it has dedicated storage to save the queues' status. The leading actor of this post will be pg-boss, an NPM library that implements the queue system thanks... Read more The post Queueing Without a Queue: The PostgreSQL Hack appeared first on Codemotion Magazine. [Next page]()