Hacker News Reader

Author here. Yes, it's all about Conway's Law. Unfortunately, it's still a law that governs all companies. Fun fact: I stopped working in projects because I mostly had to find technical solutions to organizational issues.

PS: I wouldn't call it "political" (negatively connotated) but "organizational" (statement of fact)

View on HN

'Organizational' is indeed a better way to describe it. Poor choice of words on my part.

I know where it comes from, don't worry :-)

Right. But you could avoid this whole BFF malarkey by having a team that owned and released the BE and FE themselves.

How do you do that when you have multiple teams working on separate FEs, which all need to talk to the same BE?

You exploit Conway's Law by not having separate FE teams. I think this is called the Reverse Conway Manoeuvre if memory serves

This is the purest end goal though, if you've got a large monolith or you directly consume a shared backend with a large number of teams, how do you get there? BFF is just one attempt to decouple with another layer of abstraction. Eventually you can strangle the problem on the backend.

CDC on that backend would be one way. You could stream the data out to the various teams who could then materialise a view of it within their application and then craft an API over that view.

Reply on news.ycombinator.com