Originally posted by Karthik Guru:
I have never used an in-memory database in production. Would you mind sharing the problem that you/your team were solving using the in-memory database? What was the amount data that you were looking at?
I assume that performance was a big factor and thats why you had to use an in-memory database? What w'd happen at the end of the session? does it have options to persist the data somewhere?
Actually, it wasn't a production application but a
test harness that used the in-memory database. I started it up before executing test cases, each test case initialized the database in a known state using DbUnit, and after all tests were run, I shut down the in-memory database.
HSQLDB does have two other modes as well, "standalone" and "server" if I remember correctly. The standalone mode means that you've got a private database engine running on top of a local database file. The server mode is what people usually use databases like Oracle/MySQL/PostgreSQL/DB2 for, i.e. serving possibly multiple applications.