Hi Alex, thank you for the explanation.
On Sat, 2021-04-24 at 11:59 -0700, Alex Ramos wrote: > - But I don't like database servers. > - So my idea is to move to embedded H2 with cloud backing store and > get rid of the database servers, while keeping SQL, JDBC, > JdbcTemplate, and Hibernate. This is were you lose me (pardon me, I am a Unix dinosaur): Would you not still need a single H2 "server" or service instance somewhere to dispatch messages between the client and the "cloud-storage"? Beacause you stated: > This configuration would still retain an undesirable (to me) > characteristic of a traditional RDBMS, mainly, that you have one node > (running H2) that acts as a bottleneck for all data access. > Here I have an unstated requirement: I want the ability for some > consumers to "backdoor" and read the data in the cloud backing store > directly through native APIs without going through H2. 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. Anyway, maybe I am just not understanding it well and it is certainly not on me to evangelize you. Good luck and cheers Andreas -- 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/72b9bf99fa2264d862343710e8e826b2ea405a78.camel%40manticore-projects.com.
