Bakery Schema Design

[tyt2y3]

To design a schema which will be used in our test suite, tutorial and demo web app (REST API).
Covering all datatypes (numeric, strings, currency, datetime etc) and relations (1-1, 1-N, M-N).
Some 'static data' that don't change so often (like products) and operations (like sales).
In total around 10~20 entities (excluding junction table) ?

[tyt2y3]

May be we can think about first, what the web app would do in the end?

[billy1624]

Let say a POS system? For a bakery cafe chains

[tyt2y3]

Would makes more sense if we think of a digital (eCommerce) scenario?

[tyt2y3]

Like 'Catalog' instead of 'Shelf'?

[samsamai]

What if instead of Bakery we based the web app around objects associated with 'Sea'?

[tyt2y3]

Yeah I thought of that too. But wouldn't it to be too distant from a typical use case?
Most APIs are in the category of 'OLTP'.
I was only trying to suggest an online store kind of a bakery.

[samsamai]

Yeah that makes sense. So these objects:
Bakery
Customer
Order
Cake
Bakers (or suppliers?)

[billy1624]

DIY bakery shop? Allow client to customize birthday cake for example loll

[tyt2y3]

@samsamai yes sure that makes sense. not sure about Baker / Supplier though

[samsamai]

Yeah we can drop bakers/suppliers and have shopping cart, line items, products