1

I have a Website which has a BFF (back end for front end).

It consumes data from a service (a CMS) and its own configuration data.

The CMS data and the apps config data are in separate schemas (so could be in different physical databases)

I need the BFF to decorate config data with cms data

So the options are:

  • Querying the database joining the schemas. This clearly adds coupling at the db.
  • We could replicate the data.
  • Get the data from the CMS api and aggregate in the BFF.

My preference is 3. However when arguing the case other engineers believe 1 and 3 to be just as coupled - the coupling is just moved.

My opinion is coupling at an API is looser than at a db. Also, the more things talking to the db the less easy it is to change the db schema for the CMS project.

Thoughts?

Improve this question
1
  • Since it is BFF, what are your front-ends, and what are your back-ends? A picture, as found on Sam Newman's page on BFF, would be really helpful! Commented Apr 22, 2021 at 15:24

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.