---
title: "Comment by Abhinav Sharma on \"sqlite-js-stream: Litestream, rewritten for Node\" | Hashnode"
description: "The distribution argument is the convincing one. A sidecar binary is enough friction for most small teams to just pick Postgres, but an npm install inside the a"
url: "https://hashnode.com/posts/sqlite-js-stream-litestream-nodejs/6ad77f7e602577e0904dfe0a/comment/6ad79ff464afa2d430071754"
---

[Discussion](https://hashnode.com/posts/sqlite-js-stream-litestream-nodejs/6ad77f7e602577e0904dfe0a)

Comment [sqlite-js-stream: Litestream, rewritten for Node](https://hashnode.com/posts/sqlite-js-stream-litestream-nodejs/6ad77f7e602577e0904dfe0a)

[Abhinav Sharma](https://hashnode.com/@abhinavs1920)

[Oct 20](https://hashnode.com/posts/sqlite-js-stream-litestream-nodejs/6ad77f7e602577e0904dfe0a/comment/6ad79ff464afa2d430071754)

The distribution argument is the convincing one. A sidecar binary is enough friction for most small teams to just pick Postgres, but an npm install inside the app process removes that excuse. Keeping the LTX files byte-compatible with the Go version is a smart choice too.