Actually it depends on the reader. I have chosen an architecture which is widely used nowadays and shown you the design areas you need go through when developing a relational database web application. The entire code is given as a download. So you can keep reading one chapter and browse the whole code for that chapter till you get every bit of it. I think that's the way the reader would be able to appreciate the design concepts and apply the same when designing or developing the applications in a similar architecture or a different architecture. You will find lot of articles on the net covering entity design or a full stack CRUD design. In this book I have covered all the relationships and shown you how to design the entity, business service, data access and presentation tiers. Also the user interface using JSP and JQuery/Ajax/JSON. Once you get the entire concept in this book, you can apply the same in a different technology of your choice. In conventional bottom up design model, we come up with the domain model first and then we develop on top of it using domain driven design.