I don't know if there are any strict criteria for embedded vs non- embedded.
I am running a web app using H2 in embedded mode, and it is working fine. I chose embedded mode for the following reasons: a) it is faster, as connections are within the same JVM and not over another protocol b) simple deployment c) saves some resources, as you do not need to run another JVM Here are some reasons why you may not want to run in embedded mode a) If multiple app servers need to connect to H2 b) If your database accessed so much that it makes sense to put it on another cpu altogether. c) management is a bit easier because you can use the web browser interface, but you can't easily do that when it is in embedded mode (there is a servlet which should allow you to do this, but I have not tested it yet). On Nov 14, 4:11 am, cnn <[email protected]> wrote: > What will be the criteria to decide if the database should be embeded? > I plan to develop a web application which is essentially CRUD and > reporting style > > thanks > -cnn -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
