Kurt Claeys (Ordina) was the advocate for the dataset approach while Yves Goeleven (Compuware) "preached" the Domain-Driven Design(DDD) way. Both did a good job !
Benefits (What did I learn)
- Use dataset-approach in application that needs to be build fast.
- Use dataset-approach If you are more at ease with the relational model than OO-models.
- Use a dataset to persist information on a PDA . You can use the dataset xml features for that.
- Check out the new dataset features in VS2008 . You can separate the generated TableAdapters from the dataset type in different projects. So you make a assembly with dataset types that are shared on several layers and/or tiers. There is also a "manager" that handles multi-table updates.
- Microsoft continues to invest in Datasets (VS2008 , LINQ to Datasets).
- But Microsoft also tries to keep up with the DDD camp (Entity Framework)
- There is also stuff in between LINQ to SQL
- Domain-driven design(DDD) is object-oriented design with emphasis on the problem domain. The domain model is the basis. I should catch up on that (http://www.domaindrivendesign.com/).
- DDD is difficult. Expect big learning curve.
- Don't expose domain layer immediately to UserInterface layer. You should consider other objects to transport the information of an entity (DDD for principal domain object representing something valuable for the business (customer order, etc).
- Use an ORM to help you bridge the Object-Relational mismatch
- You need involvement from all stakeholders to do DDD to practice the Ubiquitous Language principle.
Concerns (What did I miss)
- Example of DDD applications (or parts of ) to see side-by-side difference. Kurt prepared a lot of example applications to support his viewpoints.