DDD aka Domain Driven Design

In: Design Pattern| MVC

18 Mar 2009

I read an interesting post on Domain Driven Design on Fede.carg’s blog. Ever heard about Domain Driven Design ?

Domain-driven design separates the model layer “M” of MVC into an application, domain and infrastructure layer. The infrastructure layer is used to retrieve and store data. The domain layer is where the business knowledge or expertise is. The application layer is responsible for coordinating the infrastructure and domain layers to make a useful application. Typically, it would use the infrastructure to obtain the data, consult the domain to see what should be done, and then use the infrastructure again to achieve the results.

  • Digg
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks

Comment Form

Who am I?

My name is Bashar Al-Fallouji and this is my Blog. I currently work at Nstein as a Senior Solution Architect & Business Analyst. Nstein Technologies develops and markets multilingual solutions that power digital publishing for the most prestigious newspapers, magazines, and content-driven organizations.

I am particularly interested in Web applications, Open Source Development, Software Engineering, Information Architecture, Unit Testing, XP/Agile development, etc.

On this blog, you will find mostly technical articles and thoughts around PHP, OOP, OOD, Unit Testing, etc. I am also sharing a few open source tools and scripts.

  • r0b: Thanks for sharing that great script! Saved me hundreds lines of includes in my project! [...]
  • anis: Excellent Slide bashar! j'ai rate la presentation [...]
  • Apprendre a utiliser Git | Anis Berejeb: [...] chez github. essayons de « checkouter»  un projet. Je choisis le projet [...]
  • Sheila: BAF rocks! [...]
  • anis berejeb: I think that there is no ambiguity because what is passed in the : $res = changeObj($obj = new StdC [...]