Comment by Moisés Rubio Santos on "Migrating large D1 to Turso"

Hi Lukas, I may have gotten a little lost because I am not fluent in English.

But I wanted to ask you a question, the big breakthrough you have achieved with Turso is to have local copies in the clients and in that sense I understand the difference.

But knowing that D1 is no longer beta and that you talk about 2 gigs of maximum space but now I think it is 10 gigs, if you could not have those local copies, would you think about D1? I am developing a saas and I am worried about what you said about the latency and how long D1 takes when it is supposed to be designed to scale and that it would seem at first glance similar to D1.

I'm going to use cloudflare as serverless and that's why my initial idea to stay in the ecosystem but I was very concerned reading you.

Best regards

Hi Moisés, Sorry it took so long to respond!

It is really specific to your project. The latency, if you use Cloudflare Workers for accessing the database, is very low. My problem was because I was using the SQL API from a separate application. That is why Turso local copies became so valuable.

Furthermore, I didn't know when D1 will out of beta. I am happy with turso because there is no size limit, whereas D1 still has 10GB limit. My current database is already bigger than 10GB.

Another point for me is that I don't want to be vendor locked in. The perception (which really may just be a trivial illusion) that I can download the sqlite file from Turso is what makes me believe that I could move out from Cloudflare in an hour - package my worker into a Bun.serve() docker container and deploy it on my server. I may never need to do that but who knows.

I am a big fan of Cloudflare and I don't see them being bad in any way as long as it fits what you're doing. :)

Hope that helps!

Search Hashnode