# Tokio

An asynchronous runtime and event-driven, non-blocking I/O platform for Rust applications.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## A Self-Baked Async FFI Framework for Rust C# Interop

DevFeed: [A Self-Baked Async FFI Framework for Rust C# Interop](<https://devfeed.tech/articles/a-self-baked-async-ffi-framework-for-rust-c-interop-4882.md>)

Original publisher: [Read original article](<https://www.scylladb.com/2026/08/31/async-ffi-framework-for-rust-c-interop/>)

Author: Cynthia Dunlop

Published: 2026-08-31T13:00:34Z

Content type: article

Language: en

Sources: [ScyllaDB](<https://devfeed.tech/sources/scylladb.md>)

Topics: [Rust](<https://devfeed.tech/topics/rust.md>), [Tokio](<https://devfeed.tech/topics/tokio.md>), [.NET](<https://devfeed.tech/topics/net.md>), [C#](<https://devfeed.tech/topics/csharp.md>), [scylladb](<https://devfeed.tech/topics/scylladb.md>), [For the Love of Code](<https://devfeed.tech/topics/for-the-love-of-code.md>)

Tags: [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [drivers](<https://devfeed.tech/tags/drivers.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [hackathon](<https://devfeed.tech/tags/hackathon.md>), [interop](<https://devfeed.tech/tags/interop.md>), [rust](<https://devfeed.tech/tags/rust.md>), [scylladb](<https://devfeed.tech/tags/scylladb.md>)

### AI overview

The article describes ScyllaDB's effort to build a Rust-based driver architecture with thin language-binding layers, focusing on a C# driver. It explains the motivation for creating a custom asynchronous FFI framework to connect Rust's Tokio runtime with .NET's async runtime over the C ABI, after existing binding-generation tools proved insufficient for Rust-C# async interoperation.

### Source excerpt

How we got tokio and .NET's async runtime talking to each other, over the C ABI

## What We Learned Building a Rust Runtime for TypeScript

DevFeed: [What We Learned Building a Rust Runtime for TypeScript](<https://devfeed.tech/articles/what-we-learned-building-a-rust-runtime-for-typescript-17839.md>)

Original publisher: [Read original article](<https://encore.dev/blog/rust-runtime>)

Author: Ivan Cernja

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

Content type: article

Language: en

Sources: [Encore Updates](<https://devfeed.tech/sources/encore-updates.md>)

Topics: [Rust](<https://devfeed.tech/topics/rust.md>), [TypeScript](<https://devfeed.tech/topics/typescript.md>), [Tokio](<https://devfeed.tech/topics/tokio.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [Pingora](<https://devfeed.tech/topics/pingora.md>)

Tags: [building](<https://devfeed.tech/tags/building.md>), [ipc](<https://devfeed.tech/tags/ipc.md>), [latency](<https://devfeed.tech/tags/latency.md>), [performance](<https://devfeed.tech/tags/performance.md>), [pingora](<https://devfeed.tech/tags/pingora.md>), [rust](<https://devfeed.tech/tags/rust.md>), [tokio](<https://devfeed.tech/tags/tokio.md>), [tracing](<https://devfeed.tech/tags/tracing.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

### AI overview

Encore describes building a Rust runtime for TypeScript applications. The runtime moves infrastructure work such as HTTP handling, database connectivity, pub/sub, tracing, metrics, storage, caching, and API gateway functions into Rust running on Tokio, while TypeScript handles application business logic. The article also explains why an IPC-based Go sidecar prototype introduced measurable latency overhead.

### Source excerpt

67,000 lines of Rust, two years, and the non-obvious problems of making Node.js and Rust work together in the same process.

## Persistent Storage and 97% Faster Cold Starts for Edge Functions

DevFeed: [Persistent Storage and 97% Faster Cold Starts for Edge Functions](<https://devfeed.tech/articles/persistent-storage-and-97-faster-cold-starts-for-edge-functions-479.md>)

Original publisher: [Read original article](<https://supabase.com/blog/persistent-storage-for-faster-edge-functions>)

Author: Lakshan Perera; Nyannyacha

Published: 2025-07-18T07:00:00Z

Content type: release

Language: en

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

Topics: [Supabase](<https://devfeed.tech/topics/supabase.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Filesystems](<https://devfeed.tech/topics/filesystems.md>), [mount](<https://devfeed.tech/topics/mount.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [Tokio](<https://devfeed.tech/topics/tokio.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Internet of things](<https://devfeed.tech/topics/iot.md>), [Database](<https://devfeed.tech/topics/database.md>)

Tags: [boot](<https://devfeed.tech/tags/boot.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [environment-variables](<https://devfeed.tech/tags/environment-variables.md>), [files](<https://devfeed.tech/tags/files.md>), [iot](<https://devfeed.tech/tags/iot.md>), [latency](<https://devfeed.tech/tags/latency.md>), [mount](<https://devfeed.tech/tags/mount.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [s3](<https://devfeed.tech/tags/s3.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [storage](<https://devfeed.tech/tags/storage.md>), [tokio](<https://devfeed.tech/tags/tokio.md>)

### AI overview

Supabase introduces persistent storage for Edge Functions by mounting S3-compatible buckets, including Supabase Storage Buckets, as directories. The release also reports up to 97% faster and more predictable cold starts by moving workers performing initial script evaluation to a dedicated blocking pool.

### Source excerpt

Mount S3-compatible buckets as persistent file storage in Edge Functions with up to 97% faster cold start times.

## A Bug in Fly.io's Rust Anycast Router

DevFeed: [A Bug in Fly.io's Rust Anycast Router](<https://devfeed.tech/articles/parking-lot-ffffffffffffffff-1714.md>)

Original publisher: [Read original article](<https://fly.io/blog/parking-lot-ffffffffffffffff/>)

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

Content type: article

Language: en

Sources: [The Fly Blog](<https://devfeed.tech/sources/the-fly-blog.md>)

Topics: [fly.io](<https://devfeed.tech/topics/fly-io.md>), [Rust](<https://devfeed.tech/topics/rust.md>), [networking](<https://devfeed.tech/topics/networking.md>), [Tokio](<https://devfeed.tech/topics/tokio.md>)

Tags: [bug](<https://devfeed.tech/tags/bug.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [close-to-users](<https://devfeed.tech/tags/close-to-users.md>), [deploy-app-servers](<https://devfeed.tech/tags/deploy-app-servers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [fly](<https://devfeed.tech/tags/fly.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [heroku-alternative](<https://devfeed.tech/tags/heroku-alternative.md>), [heroku-competitor](<https://devfeed.tech/tags/heroku-competitor.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [i](<https://devfeed.tech/tags/i.md>), [network](<https://devfeed.tech/tags/network.md>), [networking](<https://devfeed.tech/tags/networking.md>), [postgresql-clusters](<https://devfeed.tech/tags/postgresql-clusters.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [rust](<https://devfeed.tech/tags/rust.md>), [servers](<https://devfeed.tech/tags/servers.md>), [tokio](<https://devfeed.tech/tags/tokio.md>)

### AI overview

Fly.io describes a bug in fly-proxy, its Rust Anycast router. The post explains the challenge of distributing rapidly changing routing state for apps and connections across its infrastructure.

### Source excerpt

We're Fly.io, a public cloud that runs apps in a bunch of locations all over the world. This is a post about a gnarly bug in our Anycast router, the largest Rust project in our codebase. You won't need much of any Rust to follow it. The basic idea is simple: customers give us Docker containers, and tell us which one of 30+ regions around the world they want them to run in. We convert the containers into lightweight virtual machines, and then link them to an Anycast network. If you boot up an app here in Sydney and Frankfurt, and a request for it lands in Narita, it'll get routed to Sydney. The component doing that work is called fly-proxy. It's a Rust program, and it has been ill behaved of late. Dramatis Personae fly-proxy, our intrepid Anycast router. corrosion, our intrepid Anycast routing protocol. Rust, a programming language you probably don't use. read-write locks, a synchronization primitive that allows for many readers or one single writer. parking_lot, a well-regarded optimized implementation of locks in Rust. Gaze not into the abyss, lest you become recognized as an abyss domain expert, and they expect you keep gazing into the damn thing Mathewson 6:31 Anycast Routing You already know how to build a proxy. Connection comes in, connection goes out, copy back and forth. So for the amount of time we spend writing about fly-proxy, you might wonder what the big deal is. To be fair, in the nuts and bolts of actually proxying requests, fly-proxy does some interesting stuff. For one thing, it's written in Rust, which is apparently a big deal all on its own. It's a large, asynchronous codebase that handles multiple protocols, TLS termination, and certificate issuance. It exercises a lot of Tokio features. But none of this is the hard part of fly-proxy. We operate thousands of servers around the world. A customer Fly Machine might get scheduled onto any of them; in some places, the expectation we set with customers is that their Machines will potentially start in l

## Taming A Voracious Rust Proxy

DevFeed: [Taming A Voracious Rust Proxy](<https://devfeed.tech/articles/taming-a-voracious-rust-proxy-1718.md>)

Original publisher: [Read original article](<https://fly.io/blog/taming-rust-proxy/>)

Published: 2025-02-26T00:00:00Z

Content type: article

Language: en

Sources: [The Fly Blog](<https://devfeed.tech/sources/the-fly-blog.md>)

Topics: [Rust](<https://devfeed.tech/topics/rust.md>), [fly](<https://devfeed.tech/topics/fly.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [incident](<https://devfeed.tech/topics/incident.md>), [Tokio](<https://devfeed.tech/topics/tokio.md>), [Containers](<https://devfeed.tech/topics/containers.md>), [Network](<https://devfeed.tech/topics/network.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [cpu](<https://devfeed.tech/topics/cpu.md>)

Tags: [async](<https://devfeed.tech/tags/async.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [close-to-users](<https://devfeed.tech/tags/close-to-users.md>), [containers](<https://devfeed.tech/tags/containers.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [deploy-app-servers](<https://devfeed.tech/tags/deploy-app-servers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [fly](<https://devfeed.tech/tags/fly.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [heroku-alternative](<https://devfeed.tech/tags/heroku-alternative.md>), [heroku-competitor](<https://devfeed.tech/tags/heroku-competitor.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [http](<https://devfeed.tech/tags/http.md>), [i](<https://devfeed.tech/tags/i.md>), [incident](<https://devfeed.tech/tags/incident.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [network](<https://devfeed.tech/tags/network.md>), [networking](<https://devfeed.tech/tags/networking.md>), [postgresql-clusters](<https://devfeed.tech/tags/postgresql-clusters.md>), [rust](<https://devfeed.tech/tags/rust.md>), [servers](<https://devfeed.tech/tags/servers.md>), [tokio](<https://devfeed.tech/tags/tokio.md>), [tracing](<https://devfeed.tech/tags/tracing.md>), [virtual-machines](<https://devfeed.tech/tags/virtual-machines.md>)

### AI overview

The article investigates a recurring CPU and HTTP-error incident affecting Fly.io edge proxies. Profiling reveals unexpectedly high overhead in Rust tracing's Subscriber while the proxy handles largely idle asynchronous work, leading into a review of async Rust futures and Tokio execution.

### Source excerpt

Here's a fun bug. The basic idea of our service is that we run containers for our users, as hardware-isolated virtual machines (Fly Machines), on hardware we own around the world. What makes that interesting is that we also connect every Fly Machine to a global Anycast network. If your app is running in Hong Kong and Dallas, and a request for it arrives in Singapore, we'll route it to HKG. Our own hardware fleet is roughly divided into two kinds of servers: edges, which receive incoming requests from the Internet, and workers, which run Fly Machines. Edges exist almost solely to run a Rust program called fly-proxy, the router at the heart of our Anycast network. So: a week or so ago, we flag an incident. Lots of things generate incidents: synthetic monitoring failures, metric thresholds, health check failures. In this case two edge tripwires tripped: elevated fly-proxy HTTP errors, and skyrocketing CPU utilization, on a couple hosts in IAD. Our incident process is pretty ironed out at this point. We created an incident channel (we ❤ Rootly for this, seriously check out Rootly, an infra MVP here for years now), and incident responders quickly concluded that, while something hinky was definitely going on, the platform was fine. We have a lot of edges, and we've also recently converted many of our edge servers to significantly beefier hardware. Bouncing fly-proxy clears the problem up on an affected proxy. But this wouldn't be much of an interesting story if the problem didn't later come back. So, for some number of hours, we're in an annoying steady-state of getting paged and bouncing proxies. While this is happening, Pavel, on our proxy team, pulls a profile from an angry proxy. So, this is fuckin' weird: a huge chunk of the profile is dominated by Rust tracing's Subscriber. But that doesn't make sense. The entire point of Rust tracing, which generates fine-grained span records for program activity, is that entering and exiting a span is very, very fast. If the mere

## How to deadlock Tokio application in Rust with just a single mutex

DevFeed: [How to deadlock Tokio application in Rust with just a single mutex](<https://devfeed.tech/articles/how-to-deadlock-tokio-application-in-rust-with-just-a-single-mutex-5965.md>)

Original publisher: [Read original article](<https://turso.tech/blog/how-to-deadlock-tokio-application-in-rust-with-just-a-single-mutex>)

Author: Piotr Jastrzebski

Published: 2024-09-02T00:00:00Z

Content type: tutorial

Language: en

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

Topics: [Tokio](<https://devfeed.tech/topics/tokio.md>), [Deadlock](<https://devfeed.tech/topics/deadlock.md>)

Tags: [concurrent-programming](<https://devfeed.tech/tags/concurrent-programming.md>), [deadlock](<https://devfeed.tech/tags/deadlock.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [rust](<https://devfeed.tech/tags/rust.md>), [tokio](<https://devfeed.tech/tags/tokio.md>), [turso](<https://devfeed.tech/tags/turso.md>)

### AI overview

A Tokio-based Rust program deadlocks when a synchronous task holds a std::sync::Mutex while blocking on a future. The article recommends tokio::sync::Mutex for this asynchronous scenario and cautions against premature optimization.

### Source excerpt

Battlefield story of how we managed to deadlock Tokio program with just a single mutex

## How Encore.ts combines Node.js with an asynchronous Rust runtime

DevFeed: [How Encore.ts combines Node.js with an asynchronous Rust runtime](<https://devfeed.tech/articles/encore-ts-9x-faster-than-express-js-3x-faster-than-elysiajs-hono-17797.md>)

Original publisher: [Read original article](<https://encore.dev/blog/event-loops>)

Author: André Eriksson

Published: 2024-06-17T00:00:00Z

Content type: article

Language: en

Sources: [Encore Updates](<https://devfeed.tech/sources/encore-updates.md>)

Topics: [Node.js](<https://devfeed.tech/topics/node-js.md>), [Rust](<https://devfeed.tech/topics/rust.md>), [Tokio](<https://devfeed.tech/topics/tokio.md>), [Framework](<https://devfeed.tech/topics/framework.md>), [API](<https://devfeed.tech/topics/api.md>)

Tags: [benchmark](<https://devfeed.tech/tags/benchmark.md>), [load-testing](<https://devfeed.tech/tags/load-testing.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [rust](<https://devfeed.tech/tags/rust.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tokio](<https://devfeed.tech/tags/tokio.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

### AI overview

The article explains how Encore.ts combines a TypeScript backend framework with a high-performance Rust runtime. The runtime handles HTTP I/O on a multithreaded asynchronous event loop using Tokio and Hyper, then passes processed requests to Node.js handlers while maintaining Node.js compatibility.

### Source excerpt

Combining Node.js with Async Rust for remarkable performance

## Neon Serverless Driver on JSR

DevFeed: [Neon Serverless Driver on JSR](<https://devfeed.tech/articles/neon-serverless-driver-on-jsr-5679.md>)

Original publisher: [Read original article](<https://neon.com/blog/neon-serverless-driver-on-jsr>)

Author: Raouf Chebri

Published: 2024-04-17T09:26:33Z

Content type: release

Language: en

Sources: [Blog -- Neon Docs](<https://devfeed.tech/sources/blog-neon-docs.md>)

Topics: [Deno](<https://devfeed.tech/topics/deno.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [TypeScript](<https://devfeed.tech/topics/typescript.md>), [V8](<https://devfeed.tech/topics/v8.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [Rust](<https://devfeed.tech/topics/rust.md>), [Tokio](<https://devfeed.tech/topics/tokio.md>), [Workers](<https://devfeed.tech/topics/workers.md>), [Bun](<https://devfeed.tech/topics/bun.md>), [npm](<https://devfeed.tech/topics/npm.md>)

Tags: [bun](<https://devfeed.tech/tags/bun.md>), [caching](<https://devfeed.tech/tags/caching.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [cloudflare-workers](<https://devfeed.tech/tags/cloudflare-workers.md>), [community](<https://devfeed.tech/tags/community.md>), [discord](<https://devfeed.tech/tags/discord.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [npm](<https://devfeed.tech/tags/npm.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [rust](<https://devfeed.tech/tags/rust.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [tokio](<https://devfeed.tech/tags/tokio.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

### AI overview

Neon announces Serverless Driver 0.9.0 on Deno's JavaScript Registry JSR. The driver enables database connections from Deno and other V8-isolate runtimes through WebSocket and HTTP-based protocols, with connection caching and optimized sub-10ms first-query latency.

### Source excerpt

We're excited to announce the release of Neon's Serverless Driver 0.9.0 on Deno's JavaScript Registry JSR. Deno is an open-source JavaScript, TypeScript, and WebAssembly runtime built on V8, Rust, and Tokio. Although compatible with npm, Deno built JSR to address several changes...

## Legba: An Asynchronous Rust Framework for Authentication Bruteforcing

DevFeed: [Legba: An Asynchronous Rust Framework for Authentication Bruteforcing](<https://devfeed.tech/articles/enumerate-bruteforce-attack-all-the-things-presenting-legba-41268.md>)

Original publisher: [Read original article](<https://www.evilsocket.net/2023/11/02/Enumerate-Bruteforce-Attack-All-The-Things-Presenting-Legba/>)

Author: Simone Margaritelli

Published: 2023-11-02T16:46:32Z

Content type: opinion

Language: en

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

Topics: [Tool](<https://devfeed.tech/topics/tool.md>), [Rust](<https://devfeed.tech/topics/rust.md>), [Tokio](<https://devfeed.tech/topics/tokio.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [amqp](<https://devfeed.tech/tags/amqp.md>), [async](<https://devfeed.tech/tags/async.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [bruteforce](<https://devfeed.tech/tags/bruteforce.md>), [cassandra](<https://devfeed.tech/tags/cassandra.md>), [csrf-token](<https://devfeed.tech/tags/csrf-token.md>), [dns-subdomain-enumeration](<https://devfeed.tech/tags/dns-subdomain-enumeration.md>), [http](<https://devfeed.tech/tags/http.md>), [hydra](<https://devfeed.tech/tags/hydra.md>), [imap](<https://devfeed.tech/tags/imap.md>), [kerberos](<https://devfeed.tech/tags/kerberos.md>), [kerberos-pre-authentication](<https://devfeed.tech/tags/kerberos-pre-authentication.md>), [ldap](<https://devfeed.tech/tags/ldap.md>), [legba](<https://devfeed.tech/tags/legba.md>), [mongodb](<https://devfeed.tech/tags/mongodb.md>), [mssql](<https://devfeed.tech/tags/mssql.md>), [multi-protocol](<https://devfeed.tech/tags/multi-protocol.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [ntlm](<https://devfeed.tech/tags/ntlm.md>), [offensive-tools](<https://devfeed.tech/tags/offensive-tools.md>), [oracle](<https://devfeed.tech/tags/oracle.md>), [password](<https://devfeed.tech/tags/password.md>), [pgsql](<https://devfeed.tech/tags/pgsql.md>), [pop3](<https://devfeed.tech/tags/pop3.md>), [project-release](<https://devfeed.tech/tags/project-release.md>), [rdp](<https://devfeed.tech/tags/rdp.md>), [red-team](<https://devfeed.tech/tags/red-team.md>), [rust](<https://devfeed.tech/tags/rust.md>), [tokio](<https://devfeed.tech/tags/tokio.md>), [tool](<https://devfeed.tech/tags/tool.md>), [wordlist](<https://devfeed.tech/tags/wordlist.md>)

### AI overview

The article presents Legba, a Rust-based authentication bruteforcing tool developed as an asynchronous and modular alternative to tools such as THC Hydra. It discusses the motivation, design objectives, supported features, and a limited localhost benchmark comparing Legba with Hydra.

### Source excerpt

During the last few weeks I've been working on a new tool that started as a way for me to become more familiar with Rust and its

## Introducing Apollo GraphOS

DevFeed: [Introducing Apollo GraphOS](<https://devfeed.tech/articles/introducing-apollo-graphos-23407.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/introducing-apollo-graphos>)

Author: Matt DeBergalis

Published: 2022-10-05T09:29:00Z

Content type: release

Language: en

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

Topics: [GraphOS](<https://devfeed.tech/topics/graphos.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [Tokio](<https://devfeed.tech/topics/tokio.md>)

Tags: [announcement](<https://devfeed.tech/tags/announcement.md>), [apollo](<https://devfeed.tech/tags/apollo.md>), [audit](<https://devfeed.tech/tags/audit.md>), [backend](<https://devfeed.tech/tags/backend.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [graphos](<https://devfeed.tech/tags/graphos.md>), [observability](<https://devfeed.tech/tags/observability.md>), [performance](<https://devfeed.tech/tags/performance.md>), [rust](<https://devfeed.tech/tags/rust.md>), [schema](<https://devfeed.tech/tags/schema.md>)

### AI overview

Apollo announces GraphOS, a cloud platform for building, connecting, and scaling supergraphs. It combines a supergraph runtime based on Apollo Router with control-plane, schema delivery, collaboration, and observability tools.

### Source excerpt

When we built Apollo in 2016, we had a vision. We set out to build one distributed and scalable data layer that could connect to anything we need, no matter the client, the architecture, the source, the language. It was a lofty goal, but work worth doing, because solving this gets to the heart of how to make app development more approachable and productive.