I could handle that at the application layer for a fixed number of databases but you end up predefin
I could handle that at the application layer for a fixed number of databases but you end up predefining a fixed set of databases in a wrangler config file and then accessing them in your workers. Feels strange and hard to scale. Is there a better way?
Right now, I have everything in one DB. I'd probably shard by customer account for simplicity and replicate schemas across instances. I could of course split my data in other ways but this feels the most flexible at the moment.
Right now, I have everything in one DB. I'd probably shard by customer account for simplicity and replicate schemas across instances. I could of course split my data in other ways but this feels the most flexible at the moment.
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
86,942Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
