Rule of thumb — Orderbooks are always stored in memory, not in a database. This is because they change/are accessed so quickly.
If stored in the DB, they will be accessed too frequently, causing concurrency issues and high latency.
Orderbooks need to be fast. So there are two parts of the schema design
Where are the bids stored? the asks? The last price at which the stock was traded?
