This session looks beyond the acronyms to distill the rationale behind the shift away from "anemic" domain models towards "rich" domain models. It explores several technical consequences that can arise when practicing DDD when dealing with large scale enterprise integration and SOA.
You may have overheard a confusing conversation like this before:
Developer 1: This rich domain model stuff is so hot right now. Developer 2: Yes! And value objects are evil! Thanks to DDD and Spring we don't need those anymore! Developer 1: Wait, don't you mean DTOs? Developer 2: Whatever. They're evil too! One model for them all!
This session looks beyond the acronyms to distill the rationale behind the shift away from "anemic" domain models towards "rich" domain models. It also explores consequences that can arise if you're not careful, particularly when dealing with large scale enterprise integration and SOA.
Is this myth fact or fiction? Tune in and find out!
This just in! Dependency injection improves testability. What, you mean you already knew that? While the positive effects of dependency injection on unit testing are understood, loose coupling also facilitates system, acceptance, and load testing. In this session you'll learn how to do acceptance testing with Spring and a tool called FitNesse.
Higher level acceptance and stress tests are important for meeting end user requirements. This session goes places where the others don't. You'll learn how to do acceptance testing with Spring and a tool called FitNesse. You'll also see techniques for stress testing, including using aspects to measure performance and debug issues in a production environment.