Dynamic Query Design Pattern

Allowing for Ad-hoc Querying

I added a new design pattern chapter, called «Dynamic Query Design Pattern». This design pattern problem statement goes like this:

1. Provide immediate answers

2. How you model it matters

3. Dumping everything into the lake is painful

The core challenge is enabling flexible, on-the-fly querying. The design considerations are a Universal Analytics API with four 4 layers:

1. Produces code artefacts (YAML, extended SQL)

2. Reusable, parameterized business logic

3. A logical data model that's decoupled

4. Some form of cache for sub-second responses

In the chapter, you find more: Implementation guide, real examples, use cases (including a homegrown SQLite-backed metadata store), known uses from Google’s Dremel, Netflix’s DataJunction, and more.

Check the new chapter at Dynamic Query Design Pattern: Allowing for Ad-hoc Querying. Remember, this is a paid chapter, but you get the first two parts for free.

But wait, there is more. I’ve added lots of cool technical updates:

• updated mdBook for a smoother reading experience

• added interactive graph

• added last updated date and reading time to each chapter

• RSS feed is now updated

And many more notes added to vault.ssp.sh.