Freek.dev

Very nice post by Jessica Joy Kerr on the benefits and tradeoffs of event sourcing.

We can get a complete, consistent model of a small piece of the world using Event Sourcing. This is powerful but expensive.

Read more [blog.jessitron.com]

A great post by Barry O Sullivan on what, in my mind, is one of the biggest advantages of event sourcing: the ability to create projections.

Projections are a necessary part of any event sourced or CQRS system. These systems don't rely on a single generic data source such as a normalised MySQL database. Instead you build up your data sets by playing through the events, i.e the “film”, "projecting" them into the shape you want. This allows lot of flexibility as you're no longer bound by a single data model on which you have to run increasingly monstrous SQL queries (12+ joins anyone?). With projections you can build a data model specifically for the problem/question at hand.

Read more [dev.to]

When the db structure changes, it's sometimes easy to perform the data migration inside a database migration.

Migration 1: do the db migration + restructure the data

Migration 2: drop the old columns

I'd only do this for simple stuff. pic.twitter.com/v2roA6OxBc

— Freek Van der Herten (@freekmurze) February 24, 2018

Read more [twitter.com]

The database model behind WordPress doesn’t follow several good database design rules and conventions. When we’re designing a database for a specific purpose, knowing all its desired functionalities in advance, we can follow all of those rules. But WordPress needs to cover anything that anyone could have in mind, so sacrificing foreign keys and using EAV is something that must be done.

Read more