What books have helped you understand the development of n-level

Question

Which books helped you understand the n-tier design (presentation tier, user object user interfaces, data business objects, and data sets)?

I would prefer books, but blogs and other sites are also welcome. I inherited the application developed by n-Tier in a new assignment, and although it took me a while to get used to it, I see the usefulness of the concepts. Moving forward, I want my developments to meet the same standards. Focus in C # will also be great.

Also, are there other design patterns that you would suggest for scalability? Is there any suggested reading you can provide for these design patterns?

Answer 1

Reading Enterprise Application Architecture (PoEAA) patterns were a great discovery for me. It is Internet-oriented and has a detailed understanding of how all these levels should interact.

IIRC, examples are presented in both C # and Java.

Answer 2

This is the standard list of books that I chase people in my office to read, and the order in which I would read them:

Agile Principles, Patterns and Practices in C # - Robert C. Martin, Mika Martin
Refactoring: Improving the Design of Existing Code - Martin Fowler
Effective work with outdated code - Michael Feathers
Domain Managed Project: Fighting Software Complexity at the Heart - Eric Evans
Applying Domain-Driven Designs and Templates: With C # Examples - Jimmy Nilsson

If you want to read only one book, read the book by Robert C. Martin. It will make you want to read others. The Refactoring Book is basically a catalog of methods, more of a reference than an instruction manual, but still very well worth it. If you are developing all new developments now, save the Legacy Code book for the latter.

Answer 3

Running Objects in Amazon's Visual Basic 2005 is Best For Newbies

OOP: creating reusable components with Microsoft Visual Basic.NET Amazon is also a good book

Answer 4

books are great for the specifics and details of some solutions / approaches, but the principle of separation of problems is sufficient for logical inference n- level architecture

Answer 5

Expert C # 2005 Business Objects, Second Edition

The goal is not to teach about the n-level, but building the framework suggested in the book helps in understanding how everything works in the n-level world.