Feature-Driven vs Domain-Driven

[azinit]

Hello again!

At the moment I'm in deep learning and discovering of feature-driven approach to design architecture (with practicing at work, of course).

But with time... I've been noticing similar principles and goals with Domain Driven model

And I'll glad to see different opinions at this point! =)

Main question - What are differences and similarities of feature-driven with domain-driven, on your opinion?

P.S. Especially - from @kof

[kof]

The core point of feature driven architecture is the constraints: Feature can't depend on feature, page can't depend on page and others.

Domain Driven Design is more generic

[azinit]

@kof , thanks for quick feedback!

Are you mean, that in DDD - isolating of abstractions is not so required?

Or abstractions levels aren't so explicit?

[kof]

Abstractions are defined differently and the set of constraints is more vague, more generic than I would do in FDD. at least from what I see ... there is also a lot of similarity

[kof]

We could probably see FDD as a more specialized architecture for the UI of DDD with more specific constraints

[kof]

DDD mostly talks about objects and thinks in terms of OOP, FDD is more around code organization and access rules and dependencies, rather than objects

[azinit]

Hmm, yeap - it really makes sense)

Thanks for your opinion!

Hope, that FDD really will be used more often than now(at need)

[kof]

I am afraid without a much better documentation and examples it won't be used

[azinit]

I share your opinion...
But fortunately - there are more discussions and articles about this than before

Also hope that with this initiative, we can influence and improve situation (at least - little bit)

UPD: *After finishing of work