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