margin
Home

Voice note · 2:14 · shared

Architecture discussion

You shared

Transcript

Something interesting happened during our architecture discussion today. We spent like forty minutes debating whether to split the dashboard into micro-frontends. Everyone had opinions about module federation and build times. Then someone asked, okay, who is actually going to own each piece? And nobody could answer. We ended up keeping the monolith for now. I think the whole debate was about the wrong thing.

What I understood

Your main point

“I think the whole debate was about the wrong thing.”

Details worth keeping

  • “We spent like forty minutes debating whether to split the dashboard into micro-frontends.”
  • “Then someone asked, okay, who is actually going to own each piece? And nobody could answer.”

What I noticed

I found 2 different posts in this.

One about the principle, one about the near-miss itself.

  • Architecture decisions are really ownership decisions

    Angle: Engineering thinking

  • We almost split our frontend for the wrong reason

    Angle: Story / lesson

    How do you want to approach it?

    The near-miss, told as it happened. · I'd go with this

    I have enough to start. I'll build it from your words.