On Saturday, April 24, 2021 at 11:56:07 PM UTC-7 [email protected] wrote:
> > Pardon my ignorance, but to me this looks like contradicting requirements. > Either you will use "Embedded" mode not sharing, then you can use any file > (wether local or mounted on a network does not matter). > Or you will use "Shared" mode and will rely on a kind of Service > Dispatcher, which is usually the H2 SQL Server over a TCP connection. > > It's a hybrid mode: - It's Embedded: The H2 engine is embedded (running in the same JVM as the client). So you get the benefit of not having an intermediate server. The H2 engine stores it's data (MVStore) in a cloud key-value store. This also is done without any server. You just pay a few cents for each GB of data stored. - It's Shared: Another application can use the cloud key-value store APIs directly to retrieve data, without going through H2. This has "Shared" characteristics, but only the MVStore is shared, not the H2 engine. So it's sharing at a lower layer. - Mounting a file on a network server is not the same, considering that the network server does not have an API that you can call directly to get access to the data. I don't think it's possible for two embedded H2's to share the same network filesystem. But that could solve the problem if it was possible. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/7da337ee-c2db-4f57-9a0c-d5c64c9f62e0n%40googlegroups.com.
