Sidecar

A sidecar is an architectural pattern where a separate process runs alongside a primary application to extend its functionality without modifying its core code. In the context of Tauri desktop applications, the sidecar feature allows you to bundle and spawn external binaries, such as a Python script, a Go server, or a Node.js process, alongside the main Tauri application. This is critical for custom web application development when a desktop app needs capabilities that the primary runtime cannot efficiently handle. For example, you might run a local AI inference engine as a sidecar process, or a background data sync service. The sidecar communicates with the main app through standard I/O streams or local network connections. The pattern keeps concerns separated: the frontend handles the UI, Tauri handles system integration, and the sidecar handles specialized processing.

1 How It Changed Everything

The sidecar pattern predates modern desktop frameworks by decades. It originates from service-oriented architecture in the early 2000s, where auxiliary services would run alongside primary applications in enterprise environments. The pattern gained renewed popularity with Kubernetes, where sidecar containers run alongside application containers in the same pod. Tauri adopted the term and concept around 2021 when developers needed a way to bundle non-Rust binaries with their desktop applications. The Istio service mesh, released in 2017, popularized the sidecar pattern for network proxying in microservices, which influenced how desktop frameworks later implemented similar concepts.

2 One Thing Most People Miss

The name "sidecar" comes from the motorcycle sidecar, a passenger car attached to the side of a motorcycle. Just as the sidecar extends a motorcycle's capacity without changing the motorcycle itself, a sidecar process extends an application's capabilities without modifying its core. In Tauri specifically, sidecar binaries must be placed in a specific directory structure and are automatically bundled during the build process. They receive platform-specific suffixes, meaning you can ship different sidecar binaries for Windows, macOS, and Linux within the same project configuration.

Visit: tauri.app/develop/sidecar/