Foundation DB Record Layer SQL API

Re:Foundation DB Record Layer SQL API by jwr on Thursday May 08, 2025 @02:58AM (#43923774)

Theoretically you could write your own client library, but this is nontrivial — this is a distributed database. The client library talks to multiple servers. It's not a "connect to a socket and send commands" type of client library, like in case of SQL servers.

[ Parent | on HN ]

Re:Foundation DB Record Layer SQL API by computerfan494 on Thursday May 08, 2025 @10:12AM (#43926266)

The hard part is that there is no client spec you can follow as a third-party. Everything is implementation-defined. If you're out-of-tree, your code can break at any time. If the FoundationDB project committed to a protocol, client authors could write libraries outside of the main project.

[ Parent | on HN ]

Re:Foundation DB Record Layer SQL API by jakemoshenko on Thursday May 08, 2025 @10:27AM (#43926374)

Can you though? The protocol is not very well documented and it seems to iterate rather rapidly with the server version that it aims to be compatible with.

[ Parent | on HN ]

Re:Foundation DB Record Layer SQL API by Dave_Rosenthal on Thursday May 08, 2025 @12:57PM (#43928243)

You might be able to, but are definitely not supposed to. The client is conceptually "part of the cluster".

[ Parent | on HN ]

Re:Foundation DB Record Layer SQL API by jwr on Friday May 09, 2025 @01:41AM (#43934088)

Are you planning to?

This seems to be a theoretical discussion: I don't think I'd ever want to implement the client part of FoundationDB myself, and I don't really see a good reason to.

[ Parent | on HN ]

Re:Foundation DB Record Layer SQL API by computerfan494 on Tuesday May 13, 2025 @08:40PM (#43979495)

I'm not planning to because there is no documented protocol. If there were, I might! As a result, I can't use FoundationDB.

[ Parent | on HN ]