No SQL Modelling

Question 1

What is Query Driven Modelling

Answer 1

You design your data schema starting from the exact queries you need to run — not from entities or relationships.

Question 2

Traditional (Entity-driven) modelling

Answer 2

You start with Entities and Relationships and then you write queries

Question 3

Query-driven modelling

Answer 3

You start with questions, not tables.
Get all orders for a customer in last 30 days”
“Get all orders for a restaurant today”
“Get delivery updates for an order”
Create one table per query
OrdersByCustomer(customer_id, order_time) → order_data
OrdersByRestaurant(restaurant_id, order_time) → order_data
DeliveryUpdatesByOrder(order_id, update_time) → status

Question 4

When to use

Answer 4

Queries are known and stable
Reads must be very fast
Write amplification is acceptable - Same data written to multiple tables.
Scale > flexibility