tag:blogger.com,1999:blog-7953107657166087832.post6695909157315080493..comments2024-02-05T13:55:19.560+05:30Comments on Idea Fountain: Domain driven design in SOA application stackGanesh Ghaghttp://www.blogger.com/profile/05502034961798520349noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7953107657166087832.post-52335889809675036122011-04-20T16:55:35.157+05:302011-04-20T16:55:35.157+05:30As you said that The domain driven design camp see...As you said that The domain driven design camp seems to be perfectly convinced it should reside in the domain classes. They even go on to critisize applications that do not have business logic in the domain classes. <br />And that The service driven design camp seems to think the best place for the business logic to reside is in the services, especially, the low level services<br />you say that pecial care needs to be taken in design for either case to ensure that business logic gets modelled keeping sound object oriented principles and best practices in mind.If you need to make choice which one will you usee-sign acthttp://www.arx.comnoreply@blogger.comtag:blogger.com,1999:blog-7953107657166087832.post-46140217215248927562010-07-16T12:41:38.632+05:302010-07-16T12:41:38.632+05:30Foreign keys in the database as well as number for...Foreign keys in the database as well as number formats displayed on the UI are definitely 'business' logic :)<br /><br><br />Folks don't face up to the fact that the entire application is strewn with business logic and its not necessarily a bad thing. Try to bring it all in one place and you'll end up over-engineering the solution.Ryan Fernandeshttps://www.blogger.com/profile/02730837764730410485noreply@blogger.com