Premanand Chandrasekaran > Quotes

“It is common to collectively refer to entities and value objects as domain objects.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“Axon Framework,”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“Partnership relationships between teams can lead to a situation where individual team responsibilities become very unclear,”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“not design docs or architecture diagrams – was the only equivalent to design specifications found in other engineering disciplines.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“Wardley mapping,”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“It also helps if these teams are co-located and/or have a significant working time overlap.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“Another variation of the layer cake we see commonly is one where layers refuse to share input and output types in the name of higher isolation and looser coupling.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“EventStorming,”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“we are opposed to creating additional tiers merely as a means to compensate for poorly factored core domain APIs.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“Jack Reeves in his 1992 C++ Journal article What is Software Design,”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“From that perspective, solutions that apply DDD naturally tend to be layered as well.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“It may be prudent to make use of domain events to reduce the amount of coupling between bounded contexts, making it a critical building block of DDD.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“are those aspects of the system that do not affect functionality directly but have a profound effect on the efficacy of those using and maintaining these systems.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“domain storytelling”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“The split between design and manufacturing still exists, of course, but with software, we don’t need people for manufacturing. The compiler does it for us, which means that all work the people do is design work,”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“Impact mapping provides an easy-to-understand visual representation of the relationship between the goals, users, and impacts on the deliverables.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“when coupled with data-binding constructs, makes for code that is much more readable, maintainable, and testable.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“In order to make the canvas actionable, the idea is to capture items that were most uncertain and/or risky.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“However, without some level of governance, this may quickly devolve into a big ball of mud, with layering decisions being made seemingly arbitrarily, based on personal preferences and experiences (or lack thereof).”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“There seems to exist a lot of confusion between the terms subdomains and bounded contexts. What is the difference? It turns out that subdomains are problem space concepts, whereas bounded contexts are solution space concepts.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“Aggregates are also referred to as aggregate roots, that is, the object that is at the root of the entity hierarchy. We use these terms synonymously in this book.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“Under the right circumstances, this can accelerate the growth of a business considerably while allowing the owner to retain ownership, reduced taxes, and lower interest rates.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“CAP theorem. The theorem postulates that distributed systems can either be highly available or consistent in the event of a network partition, not both at the same time. Given the three characteristics, consistency, availability, and partition tolerance, the theorem postulates that distributed systems can either be highly available or consistent in the event of a network partition, not both at the same time.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“Financial debt is the act of borrowing money from an outside party to quickly finance the operations of a business—with the promise to repay the principal plus the agreed-upon rate of interest in a timely manner. Under the right circumstances, this can accelerate the growth of a business considerably while allowing the owner to retain ownership, reduced taxes, and lower interest rates. On the other hand, the inability to pay back this debt on time can adversely affect credit rating, result in higher interest rates, cash flow difficulties, and other restrictions.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“In such scenarios, it may be worth considering consciously allowing one or more layers to be bypassed.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“While such translations may be necessary across bounded contexts, teams should strive to avoid the need for variations in names and structures of the same concept within a single bounded context. The intentional use of ubiquitous language helps avoid such scenarios.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“evolve mature software solutions that will stand the test of time.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“Consistent use of the common, ubiquitous language helps reinforce a shared understanding and produce solutions that better reflect the mental model of the domain experts.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“If the objects being translated are more or less structurally identical, we have an anemic translation.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems

“there are three types of developers implementing microservices. Those who use DDD, those who don’t realize they do, and those who fail.”
― Premanand Chandrasekaran, Domain-Driven Design with Java - A Practitioner's Guide: Create simple, elegant, and valuable software solutions for complex business problems