Floreant POS uses Apache Derby as its native DB platform but it could be easily ported to other DB. The reason we prefer Apache Derby is because of light memory foot print.  For more check out the Interesting comparison  in our blog. We discouraged portability time on supporting many dartabases because nobody may be using that in real life. For example Oracle or Postgres might be overkill for standard restaurants.

Database Schema
 There are 5 sets of tables. We followed self-explanatory names for tables and their fields. 

• Menu and Food Master database
• Restaurant & Terminal Configuration
• Ticket and Cash drawer managment
• Transaction and Payment Records
• Daily Activity  and transaction log

ER DiagramManually Accessing Database
For database modelling we use AqaFold Data Studio. (Thanks ADS team for providing us a free license). If you are a developer you may sneak peek database tables in the following steps

• Start Aqua Data Studio
• Main Menu -> Server -> Create new server
  
• Select Apache Derby database and Put "app/sa" for Login Name and Password respectively.
• Connect to server and Select Floreant POS > Tables