Also, I assume you use the [Sessions API](https://developers.cloudflare.com/d1/best-practices/read-r
Also, I assume you use the Sessions API. Otherwise, all your requests will go to the primary regardless if you have enabled read replication or not.
This is not concrete. What is quiet, and what is "still receiving queries from all over"?What I was trying to convey is that there is consistent non-zero traffic in every region, and that I expected read replicas in every region to be queried. "Quiet" as in "not enough to overload the primary DB".
.withSession() calls to my worker and see what happens. Thanks again.Your application can use read replicas with D1 Sessions API.
Hi im a noob to d1 and my biggest concern is obviously avoiding something like tea app disaster.What is the "tea app disaster"?
What is the "tea app disaster"?Recent data breach from an app called Tea: https://www.bbc.com/news/articles/c7vl57n74pqo



"db:push": "drizzle-kit push --config=./drizzle.config.ts",

.withSession()Your application can use read replicas with D1 Sessions API."db:push": "drizzle-kit push --config=./drizzle.config.ts"import { defineConfig } from "drizzle-kit";
import { config } from "dotenv";
config({
path: ".env.stage"
});
export default defineConfig({
schema: ["./src/app/schema.ts", "./src/app/auth-schema.ts"],
out: "./drizzle/app",
dialect: "sqlite",
driver: "d1-http",
dbCredentials: {
accountId: process.env.CF_ACCOUNT_ID,
databaseId: process.env.CF_DATABASE_ID,
token: process.env.CF_TOKEN,
url: ""
}
});