rcmnd

The GuardianCompany

UK news publisher; its developer blog covers the engineering behind theguardian.com.

Also onwiqqi, about them

7 things

PostgreSQLSoftware

recommended

Another great thing about Postgres is how mature it is: every question we wanted to ask had in most cases already been answered on Stack Overflow.

Why the Guardian moved its CMS content store from MongoDB to PostgreSQL on Amazon RDS

2018-11-30·theguardian.com ↗

ReactSoftware

uses

We’ve rebuilt it using React and Typescript and whilst it looks pretty similar to our old website, what’s underneath is all new.

The Guardian rebuilt theguardian.com on React and TypeScript

2019-12-08·theguardian.com ↗

TypeScriptSoftware Microsoft

uses

We’ve rebuilt it using React and Typescript and whilst it looks pretty similar to our old website, what’s underneath is all new.

2019-12-08·theguardian.com ↗

PostgreSQLSoftware

uses

We use Amazon’s RDS (Relational Database Service) to store our data in a PostgreSQL database.

A Guardian service storing data in PostgreSQL on Amazon RDS

2019-12-02·theguardian.com ↗

ScalaSoftware

uses

We wrote a proxy in Scala using Akka Streams

The Guardian built its Mongo-to-Postgres migration proxy in Scala

2018-11-30·theguardian.com ↗

BrazeSoftware Braze

uses

A library of React components for displaying Braze messages on DCR and frontend.

The Guardian's own open-source library for rendering Braze in-app messages and content cards on theguardian.com (undated README). (undated page)

github.com ↗

Amazon DynamoDBService

mixed

Unfortunately at the time Dynamo didn’t support encryption at rest.

DynamoDB was the obvious choice for the Guardian CMS migration off MongoDB but lacked encryption at rest

2018-11-30·theguardian.com ↗

MongoDBSoftware

disliked

It also didn’t deliver on its “one-click upgrade” promise, due to changes in the authentication schema between different versions of Mongo DB.

Why the Guardian moved its CMS content store off MongoDB and its OpsManager tooling

2018-11-30·theguardian.com ↗

Every entry is a verbatim quote and a link to the public post it came from. Nothing is paraphrased. If it is not on record somewhere public, it is not here.

The verdict is what they actually said: loved and liked are explicit; recommended means they told others to get it; uses means they only say they use it; read is a book on their public shelf with no verdict; mixed and disliked are kept too.

A dashed affiliate link, sponsored or their own label means the post disclosed a relationship. It is shown, never hidden.

The shading behind a date shows how dated a recommendation is for its kind of thing.

The shading behind a date shows how dated a recommendation is, for its kind of thing. Fully green is recent. It drains a quarter at a time as the post gets older, and is empty once it reads as dated.

What counts as old depends on the thing. A laptop praised four years ago has been replaced twice; a book loved twenty years ago is probably still loved. The shading is gone after about:

Stripes mean the post carries no date and the date shown is an estimate. No date at all, no shading.