Data

There are quite a few tools to avoid *needing* a database these days, static site generators chief among them. So then what are the things that push toward or require a database?

Realtime applications (or games!), where multiple users are working at once and the state of the app needs to be in sync with each other and persisted, is more and more a common need and expected feature. But it’s not simple. There are products to help (PouchDB for data and Ably for messaging come to […]

Imagine this simple data set: Norway Denmark Sweden 2004 5 4 13 2002 8 10 15 Pretty simple, but there is interesting stuff going on. Someone might be trying to reference an individual bit of information, but they also might be looking to compare data, or look at the rate of change of the data […]

TanStack Start enhances the TanStack Router by adding a server layer that improves performance through server-side rendering (SSR) and isomorphic loaders.

Drizzle ORM is a powerful object-relational mapper that combines SQL capabilities with a strongly typed API, enabling complex queries. Here we’ll look at using it’s ability to help with migrations, both code-first and database-first.

TanStack Query, or react-query, simplifies client-side data fetching with features like caching, automatic re-fetching, and error handling. It integrates smoothly with TanStack Router, allowing efficient prefetching and loading states using hooks like useSuspenseQuery.

TanStack Router is one of the most exciting projects in the web development ecosystem right now, and it doesn’t get nearly enough attention. It’s a fully fledged client-side application framework that supports advanced routing, nested layouts, and hooks for loading data. Best of all, it does all of this with deep type safety. This post […]

Drizzle is a new ORM tool that blends traditional ORM querying with a typed SQL API. Drizzle supports various databases (Postgres, MySQL, SQLite) and aims to simplify SQL crafting while avoiding common ORM pitfalls.

Let’s get into the challenges and strategies of loading data in web applications, focusing on the comparison between client-rendered sites and server-rendered applications. There are some clear negative performance impacts of SPAs and server-rendered apps are *usually* better here, except when data is slow. Then what?