Hello!� I'm a recent graduate, out in the real world... sort of.� It's just me and one other guy (who graduated even more recently than I did) doing development.Some issues that we had with adding web services to our website got me thinking about System Architecture, and I figure asking here is probably the best way to go.Basically, when I first developed our website (with ASP.NET) I *thought* that I had built a domain layer.� I had domain objects that represented concepts in the system, I had created objects that handled validation, common tasks, etc... but the longer I worked on projects outside of school, the more I realized that I was missing something.These "domain objects" that I felt so good about when I first built them now feel like they're not domain objects at all.� They're thin wrappers for ADO.NET: they expose properties, a "CreateNew" method, an "Update" method and a "Delete" method, and perform validation before updating takes place.� In practice, ...
Go to the complete details ...