Using Googles Firebase Realtime Database enables us working with a NoSQL database pattern. Firebase comes along with an observer design, to watch actively on changes within the consumed data model. This allows realtime update of data displayed in the application during runtime without a manual reload.

The general structure for using the firebase database is essential to organize the data access from the application to the database.

Structure

Since we'll start with one database scheme for the development we have at least two options to represent a customer separation.

Option A - using tenants

• dev-customer

tenants

development

members, groups, events

• other-customer

tenants

customer1

members, groups, events

Option B - without tenants

• members
• groups
• events