Nice to see more possibilities in this space, database branches look particularly interesting and useful for the JAMstack world! That's definitely something tha

Nice to see more possibilities in this space, database branches look particularly interesting and useful for the JAMstack world! That's definitely something that's hard to manage in CI/CD for JAMstack apps. It's also interesting to see more database services support HTTP APIs. SingleStore recently launched support for an HTTP API as well (https://docs.singlestore.com/managed-service/en/reference/http-api.html https://docs.singlestore.com/managed-service/en/reference/ht...). I think most database services should follow suit due to how popular serverless frameworks are becoming, and the need to have connectionless pooling. I have some questions such as: * Will all these HTTP APIs support most authentication methods already used by these database services? Or will they likely only support some sort of API token based auth? * Could HTTP caching ever be useful for these? Or just internal database caching? * Is security a concern any more so than with regular TCP connections? * Will all your typical ORMs "just work"? I think the answer is "yes", but there are some more modern ORMs that I wouldn't be too sure about (e.g. Prisma). Disclaimer: I work at SingleStore, which is a database service for data-intensive apps as well.