Hello @koviac, I would suggest having a relational database as developing a scalable application begins with an optimized data architecture. While a single “flat” table is simple to set up, it often leads to data redundancy and maintenance challenges as your app grows.
In a Single Table (Flat) structure, all data points, even those that repeat are stored in one place. For example, an “Orders” sheet might repeat a customer’s full address every time they make a purchase. This leads to data redundancy and increased risk of entry errors.
In a Relational Database, data is categorized into logical tables (e.g., Customers, Orders, Products). These tables are connected through References, ensuring that each piece of information is stored exactly once. This architecture provides:
-
Data Integrity: Update a customer’s phone number in one place, and it reflects across all related orders.
-
Navigation: Seamlessly jump between a product and all orders that include it.
-
Efficiency: Smaller, focused tables improve app performance and sync speed.
Please refer to this video and the support article for more information.