Comments on: Battling complexity in large web applications http://blog.jteam.nl/2009/10/20/battling-complexity-in-large-web-applications/ Keep updated on what we're doing! Wed, 10 Mar 2010 09:00:26 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Machiel Groeneveld http://blog.jteam.nl/2009/10/20/battling-complexity-in-large-web-applications/comment-page-1/#comment-935 Machiel Groeneveld Thu, 22 Oct 2009 13:21:32 +0000 http://blog.jteam.nl/2009/10/20/battling-complexity-in-large-web-applications/#comment-935 Nice post! I think some people make the mistake of creating a single domain model to avoid duplication. You suggest correctly to create several domains (modules) that are internally consistent but have loose coupling to other domains, even if this means duplication bits of data on the boundary or interface level. Nice post! I think some people make the mistake of creating a single domain model to avoid duplication. You suggest correctly to create several domains (modules) that are internally consistent but have loose coupling to other domains, even if this means duplication bits of data on the boundary or interface level.

]]> By: David Hobbs http://blog.jteam.nl/2009/10/20/battling-complexity-in-large-web-applications/comment-page-1/#comment-910 David Hobbs Tue, 20 Oct 2009 19:48:01 +0000 http://blog.jteam.nl/2009/10/20/battling-complexity-in-large-web-applications/#comment-910 You raise good points on how to architect for complexity, and am a fan in reducing complexity whenever possible. I would just add that one role (under project environment as a cause of complexity) that is very important, but often overlooked, is the product manager (as opposed to project manager) who is attempting to *define* the system, taking all the constraints/business realities in mind. The direction set by a strong product manager can help. Thanks, -- David You raise good points on how to architect for complexity, and am a fan in reducing complexity whenever possible. I would just add that one role (under project environment as a cause of complexity) that is very important, but often overlooked, is the product manager (as opposed to project manager) who is attempting to *define* the system, taking all the constraints/business realities in mind. The direction set by a strong product manager can help.

Thanks,

– David

]]>