Unfortunatelly, there are not so many attempts to describe #DDDesign on the #Frontend (and there should be!). That's why I'm very happy when I see a #Frontend expert @ducin.dev takes his approach on that matter! #DDDesign on the #Frontend is a thing! (BTW, @ducin.dev pls continue!) - ThreadSky

pwyczes.patternapplied.com • 80 days ago

Unfortunatelly, there are not so many attempts to describe #DDDesign on the #Frontend (and there should be!).

That's why I'm very happy when I see a #Frontend expert @ducin.dev takes his approach on that matter!

#DDDesign on the #Frontend is a thing!

(BTW, @ducin.dev pls continue!)

Reposted from Tomasz Ducin

#aDDDvent: day 1 📆🎄

If you think you're doing DDD by following a certain technology/framework/toolstack/pattern/etc, you're doing it wrong.

👉 DDD is not about technology 👈

DDD is about collaboration and communication.

Full writing ✍️ below
#DDD #DDDesign #react #angular #vue #frontend

Comments

borar.bsky.social•79 days ago

Why would DDD make sense in the front-end? What does it mean to have DDad in the front-end even?

pwyczes.patternapplied.com•79 days ago

Task-based UI, composite UI, modular UI, mobile apps, microfrontends.
Should I continue?

ducin.dev•79 days ago

also (more general):
because every frontend dev thinks their codebase is modular and yet 3 years later the same peopleconsider it legacy legacy and want to rewrite it from scratch?

borar.bsky.social•79 days ago

But Thomasz, you write that DDD is about collaboration and communication. While now you are talking about technical aspects like modularity and maintainability. I don't understand.

pwyczes.patternapplied.com•79 days ago

It's all connected. :)

ducin.dev•79 days ago

@borar.bsky.social can you phrase exact question(s)? As for now i see that you don't yet know what the reasoning is but you're already against it 😉

I'll happily discuss, let's start with making questions more precise.

BTW what is your background?

borar.bsky.social•79 days ago

We had this discussion already recently :) I still strongly claim that if you do DDD in the front-end, then logic leaked into it from thr back-end. If it's not really a front-end but a fat client, then no problem. Otherwise, the basic rule of separating (business) logic and UI is broken.

borar.bsky.social•79 days ago

Also, please explain more exactly what you mean by DDD in the front-end before promoting it like it's a self-explanatory and most logical thing to do. Is it like having a domain model in the front-end, "aggregates", something else?

ducin.dev•79 days ago

The answers in depth are in the posts linked above by Piotr.

No, no aggregates on frontend. Nearly no tactical DDD on frontend whatsoever.

Sand yes, domain model - yes.

But one doesn't equal the other.

Comments

Posting Rules

Reply