From a4d393d25991a4cdfb399380d53ff38439ad823d Mon Sep 17 00:00:00 2001 From: chao-xian Date: Thu, 3 Aug 2023 16:41:03 +0100 Subject: [PATCH] Add ADR 002 which partially pivots on ADR 001 --- docs/ADR/002-pivot-how-we-port-to-postgres.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 docs/ADR/002-pivot-how-we-port-to-postgres.md diff --git a/docs/ADR/002-pivot-how-we-port-to-postgres.md b/docs/ADR/002-pivot-how-we-port-to-postgres.md new file mode 100644 index 00000000..fe2c7c7a --- /dev/null +++ b/docs/ADR/002-pivot-how-we-port-to-postgres.md @@ -0,0 +1,13 @@ +# ADR 002 - Pivot on how we port to PostgreSQL + +## Context + +This partially reverses the approach outlined in [ADR 001](001-porting-to-postgresql.md). We were going to piggy back on work by the Publishing Team who are building a proxy app to split requests between old and new router/router-api and content-store. However they've hit several issues and can't get it working. + +On recommendation from the Tech Lead of the Platform Engineering team we are going to just use feature flags to manage the roll out. + +For feature flagging we will check for the presence of an environment variable. The default behaviour will be to use MongoDB if the variable isn't set or does not have the value "postgres". The variable should be called "ROUTER_USE_DB" and the values "mongo" or "postgres" to be absolutely clear. + +## Status + +Accepted \ No newline at end of file