What things would you not put on the db but on other service for example, i'm aware of objects/files I was planning on using cloudflare images/R2 but maybe you have some suggestions?
Just thinking out loud here but if I were to create the database manually before hand, when in my case a new organisation register check for the first empty database and assign that way. You reckon that would be possible?
Not quite, since the D1 Layer that is on top of SQLite handles simultaneous connections. It can't actually process multiple requests simultaneously, but it can store requests in a queue. I would note too that while you can use D1 outside of Cloudflare, it isn't meant to be used that way, and thus it is a bit unergonomic
They do. No matter the underlying protocol, an outgoing I/O op is counted as a "request"(though opening a TCP socket is a single connection, even if you do multiple things with it)
As I undertood, this is mostly limits impose by cloudflare that can be increased by a request or paying. But not about the technology the database uses, right?
Not necessarily. While some of the limits are applied by Cloudflare directly, others are in place because the database may not be stable above those limits. You might be able to push it farther, but CF can't guarantee that it will function correctly, so you can't raise the limit that far
Oh yeah, if you do a batch with reused statements especially, it’s in the 100s of thousands of inserts per call in a lot cases. Performance wise is really good.