Databases, content models, migrations and backups, analytics, and how to keep your data yours.

For most business sites and apps, SQL. A relational database like PostgreSQL enforces the shape of your data and can answer questions you had not thought of when you designed it. NoSQL earns its place at very large scale, or when records genuinely have no fixed shape.

A data model is the decision about what things exist in your system, what fields each one has, and how they relate to each other. It takes an afternoon to sketch and it governs what the software can do for years afterwards, which is why skipping it is the expensive option.

A content model is the set of content types a site has and the fields inside each: a service with a name, a summary and three benefits; a case study with a client, a date and images. It is the structure of your content, separate from whichever tool you edit it in.

A page builder stores a finished layout. Structured content stores the facts and decides the layout when the page is rendered. The difference only appears when you want that content somewhere else: a listing, an email, an app, or a rich search result, none of which a stored layout can supply.

A migration is a recorded, repeatable change to the shape of a database: adding a column, splitting a table, changing a type. It is written as code and applied in order, so the same change runs identically on a developer's machine, on staging, and in production.

You restore one. A backup nobody has ever restored is a file, not a backup. Pick a date, restore it somewhere that is not production, and open the result to check the data is actually there and readable. Until you have done that once, you do not have a backup, you have a hope.

Third-party analytics such as GA4 sends visitor data to somebody else's servers and gives you their reports. First-party analytics keeps that data on infrastructure you control. The trade is between depth of features and who holds the record of who visited you.

Keep the aggregate reports for as long as you like and the raw visitor-level data for as short a time as answers your questions. GA4 lets you set event retention to either 2 or 14 months, and the longer setting is not automatically better if nobody ever queries past a year.

Test it before you need it. Most platforms have an export button, and the question is what comes out of it: a usable database, or a folder of HTML with the structure stripped away. Export your content today and open the file. That five-minute check is the entire answer.

Lock-in is not a contract, it is the cost of leaving. It is measured in work: rebuilding a content model, re-entering records by hand, replacing an integration, retraining a team. A platform with no contract and no notice period can still be very hard to leave.