Separating the DDW Frontend from the Backend - own repos

[edwinmp]

Currently, the the BE and FE of the DDW exists within this singular code repo. They are thinly coupled, with the FE accessing the BE via an API. Still, this coupling, loose as it is, presents some maintenance problems that could justify decoupling them entirely into separate repos.

Clear pros & cons below - will add others as mentioned in the comments.

PROS

• More maintainable code
• Greater extensibility and easier optimisation with tools like GraphQL & DataLoader
• Better and more efficient CI processes e.g. e2e tests
• Non-parallel planning for the BE & FE
• Connect required API to FE allowing easier testing of FE changes on production data i.e. we can configure local instance of the DDW to connect to the production/staging API

CONS

• A little dev time (about a sprint, likely less) - The loose coupling makes this bit easier.
• An extra repo or two to manage