Query-driven design suits me well because I am particularly susceptible to over-engineering when I'm thinking about entities first.
-
-
Replying to @generativist
My experience with database normalization: Look at my beautiful normalized data model! Day 1 of prod load: OMG I can’t maintain this constraint without purging daily non-aggregate data without it taking more than a day. Also my joins are killing page caching. Denormalize now!
1 reply 0 retweets 2 likes -
Replying to @jmsl @generativist
Those sentences almost made sense. Production is a battle, normalization is a battle plan, and it rarely survives the first shot. — note that my experience is with real time analytics based on transactions.
1 reply 0 retweets 2 likes -
Replying to @jmsl @generativist
Traditional databases optimize for OLAP, or OLTP but not both at the same time. OLTP is writing log structured data as fast as you can. OLAP is about normalization. It’s hard to do both without slowing down writes to maintaining indices and support real time aggregation.
1 reply 0 retweets 2 likes
This is a great compression I think
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.