About the Talk
July 18, 2012 5:00 AM
A lot of applications try to focus on one large model and attempt to achieve maintainability through layers of abstraction. They use repositories, services, DALs and what not to achieve what is generally known (and feared) as Big Balls of Mud. Yet all these abstractions do not lead to maintainable solutions. And this very often leads to complicated versioning and eventually large rewrites. Can we not avoid this? Are Balls of Mud really a bad idea? When can they be good? How can we create architecture that reflects the business needs - and that evolves with them? In this session we will see if we can.