Facebook Twitter Pinterest
  • Alle Preisangaben inkl. MwSt.
Nur noch 9 auf Lager (mehr ist unterwegs).
Verkauf und Versand durch Amazon. Geschenkverpackung verfügbar.
Microsoft® .NET: Architec... ist in Ihrem Einkaufwagen hinzugefügt worden
+ EUR 3,00 Versandkosten
Gebraucht: Sehr gut | Details
Verkauft von MEDIMOPS
Zustand: Gebraucht: Sehr gut
Kommentar: medimops: schnell, sicher und zuverlässig. Gelesene Ausgabe in hervorragendem Zustand.
Möchten Sie verkaufen?
Zur Rückseite klappen Zur Vorderseite klappen
Hörprobe Wird gespielt... Angehalten   Sie hören eine Hörprobe des Audible Hörbuch-Downloads.
Mehr erfahren
Alle 3 Bilder anzeigen

Microsoft® .NET: Architecting Applications for the Enterprise (PRO-Developer) (Englisch) Taschenbuch – 15. Oktober 2008

3 von 5 Sternen 2 Kundenrezensionen

Alle Formate und Ausgaben anzeigen Andere Formate und Ausgaben ausblenden
Neu ab Gebraucht ab
Kindle Edition
"Bitte wiederholen"
"Bitte wiederholen"
EUR 42,38
EUR 39,17 EUR 0,86
7 neu ab EUR 39,17 11 gebraucht ab EUR 0,86

Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.

  • Apple
  • Android
  • Windows Phone

Geben Sie Ihre E-Mail-Adresse oder Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.

Jeder kann Kindle Bücher lesen — selbst ohne ein Kindle-Gerät — mit der KOSTENFREIEN Kindle App für Smartphones, Tablets und Computer.




To deliver the right solutions for increasingly complex enterprise and user requirements, you need vision. You need guidance. You need to apply the patterns and practices that by design create explicit outcomes for often-implicit challenges. In this book, you ll take a structured, realistic approach to resolving software complexity that places architectural integrity at its core. The authors share their extensive, real-world experience with enterprise and service-oriented development to illuminate the patterns, principles, and techniques for producing more-effective solutions, including the modeling techniques that ensure your architecture fully and explicitly addresses user requirements. They deftly cover essential concepts (UML, design patterns), the core system (business, services, data access, and presentation layers), and specific tools, including Microsoft .NET Framework and Microsoft Visual Studio(r) and they provide code samples and expert insights you can apply right away to your own .NET-based enterprise solutions.

Über den Autor und weitere Mitwirkende

Dino Esposito is a well-known ASP.NET and AJAX expert. He speaks at industry events, including DevConnections and Microsoft TechEd, contributes to MSDN' Magazine and other publications, and has written several popular Microsoft Press books, including Microsoft ASP.NET and AJAX: Architecting Web Applications.

Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?

In diesem Buch

(Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
Hier reinlesen und suchen:


3.0 von 5 Sternen
5 Sterne
4 Sterne
3 Sterne
2 Sterne
1 Sterne
Beide Kundenrezensionen anzeigen
Sagen Sie Ihre Meinung zu diesem Artikel


Format: Taschenbuch
I was reading Dinos and Andrea's book during my holydays in Italy. It is one of the best books I read in the last few months. I'm especially pleased, that this book brings the concepts and patterns from Eric Evans Domain-Driven Design: Tackling Complexity in the Heart of Software, which I by the way read during my holydays last year, and Martin Fowler Patterns of Enterprise Application Architecture closer to the developers. I'm running a small software production company (see YouTube enventionag) and I just ordered 13 copies of this great book to get each of my developers a personal copy.
Kommentar Eine Person fand diese Informationen hilfreich. War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen
Missbrauch melden
Format: Taschenbuch Verifizierter Kauf
Nach ein paar Seiten des Buches kam mir der erste Gedanke: Das kennst Du doch irgendwoher. Nach ein paar weiteren Seiten, kam der Gedanke wieder.
Wieder ein paar Seiten später, dann der Hinweis des Autors selbst. Es ist ein Werk, das permanent auf Martin Fowlers Architektur Muster verweist.

Das Buch bietet inhaltlich wenig neues, wenn man Martin Fowlers Architektur Muster kennt. Mir ist nicht klar warum der Autor dieses Buch geschrieben hat. Es ist wohl eine Art Homage an Fowler. Ich empfehle das Original zu kaufen.
2 Kommentare Eine Person fand diese Informationen hilfreich. War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen
Missbrauch melden

Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)

Amazon.com: HASH(0x9d4562d0) von 5 Sternen 50 Rezensionen
54 von 57 Kunden fanden die folgende Rezension hilfreich
HASH(0x9d46de4c) von 5 Sternen Nice book, here is the Table of Contents 23. Dezember 2008
Von Amazon Customer - Veröffentlicht auf Amazon.com
Format: Taschenbuch
This book seemed really promising from the title and mainly its author (Dino Esposito), who is one of the best .NET writers out there. It took me a while to buy it though, because for weeks I tried in vain to find its table of contents, to know exactly what I was buying. Having failed at finding one, I decided to just take a chance and buy it anyway, and I don't regret, it is a good book.

I would say the target audience is intermediate to senior developers who are getting into software architecture, or architects who work on a database-centric way and want to get an update to the current buzzwords, such as domain model pattern, repositories, services, AOP, POCO, OR/M, DDD etc. This book does not try to be a definitive source on any of those topics, but more like an introduction and a reference; the authors make a good job at pointing for resources for those who want to get more dense information.

Books like Martin Fowler's "Patterns of Enterprise Application Architecture", the GoF classic Design Patterns book and Eric Evan's "Domain-Driven Design" are mentioned dozens of times, so people who have already read those books may not have lots of new stuff to see here, unless they are looking for a lighter reference or want to see how some of those ideas can be applied on .NET.

So, for those like me who have spent a few days on Google trying to find out the book's ToC, here is a summarized version, with some of the topics covered in parenthesis:

Part 1 - Principles

1 - Architects and Architecture Today (software life cycle, agile methodologies etc)
2 - UML essentials (UML models and usage, use-case diagrams, class diagrams, sequence diagrams)
3 - Design Principles and Practices (OOD, AOP)

Part 2 - Design of the System

4 - The business layer (transaction script pattern, table module pattern, active record pattern, domain model pattern, DDD)
5 - The service layer (service layer pattern, remote façade pattern, adapter pattern, SOA, AJAX service layer for rich web frontends)
6 - The data access layer (plugin pattern, Inversion of Control, data context, query services, concurrency, lazy loading, OR/M, stored procedures, dynamic SQL)
7 - The presentation layer (MVC, MVP, presentation model pattern, choosing a UI pattern, MVP in web presentations, MVP in Windows presentations)

8 - Final thoughts
19 von 19 Kunden fanden die folgende Rezension hilfreich
HASH(0x9d46dea0) von 5 Sternen This book will not leave my side... until the 2nd edition... 4. Dezember 2008
Von T Anderson - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
This book does a great job of putting architecture into a view that .NET developers and architects can relate to.

The book covers design principles and patterns, and then relates them to each layer of a traditional layered system. It includes business, services, data access, and presentation layers. The authors include several different patterns for each layer and discuss the pros and cons of each.

The book focuses on the technical aspects of .NET architecture. It does not cover the soft skills need to be an architect, or cover the customer facing skills need to communicate with the business stakeholders. You won't find much on process either, just an overview. These missing topics have not taken away from the book, they have made it a stronger book. There are plenty of resources on how to execute the soft skills and architecture process. This book concentrates on how to communicate with the development team through solid design and well known patterns and principles.

This is a must read for all architects, no matter what your skill set is.

A .NET developer looking to move into architecture should make this book their first stop on a long journey. This will definitely get you off to a very strong start.

This book will not leave my side... until the 2nd edition...
31 von 35 Kunden fanden die folgende Rezension hilfreich
HASH(0x9d471804) von 5 Sternen If you want to know the current .NET architectural trends, this is a must read 1. Januar 2009
Von James Ashley - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
It is a misconception that architecture is a fully understood field. Like the rest of us in the relatively young discipline of software development, architects are making their way along with rules of thumb, buzzwords and trends, too, and doing their best to tie them all together.

Microsoft has always been a bit lacking when it comes to providing guidance for developing complex software. The alt.net crowd promised to fill in this lacuna, and even promoted itself in terms of filling in the blanks that Microsoft leaves in its technology offerings. However the results have been, I think, that the contemporary architect simply has more pieces to try to put together, and even more things to try to figure out.

Dino Esposito, in "Architecting Applications for the Enterprise", tries to make sense of this technical jigsaw puzzle by building on top of the core architectural concepts of layering and decoupling applications. He then takes these principles forward by seeing how the newest technologies and techniques -- WPF, WCF, Windsor, NHibernate, Entity Framework, MVP, MVC, etc. -- can fit together to form a mature enterprise application.

In many ways he cuts through much of the hype and provides insights into why you might want to use these technologies. He is comprehensive in treating each of the various Microsoft and non-Microsoft tools soberly, explaining the pros and cons of each.

Best of all, he tries to consolidate in his appendix all of his insights into a core set of architectural principles, one of which he reiterates throughout the book: the job of the architect is to reduce complexity, not increase it. It sounds simple, but many architects tend to forget this.

Mr. Esposito's final product is a synoptic view of the current state of software architecture. If you want to know what is currently thought of as best practices in enterprise architecture, then you need to read this book. It will either give you an idea of where you need to be, if you are just starting out, or reassure you that you are on the right track, if you have been following the trends of the past two or three years.

The only weakness I found in the book is perhaps the problem that these various tools don't always fit together nicely. For instance, I'm doubtful that ORMs really makes sense anymore if we decide to place them behind service layers. SOA and ORMs rose out of really different architectural problems, and provide somewhat incompatible solutions. Likewise, while the MVP pattern is very nice (we are curently using it on an enterprise project), it tends to break down when you attempt to apply it to anything complex, such as an object graph with more than two or three levels of dependent objects.

The book also recommends using interfaces extensively in order to promote testability, but on looking a little closer, this appears to be tied to a specific tool, Rhino Mock, which requires interfaces to be useful, rather to any particular architectural principle -- for instance, TypeMock doesn't require interfaces, but of course it also isn't free. Should your architecture really be tied to a tool in this way, or would it be better to find tools that support your architecture?

I tend to think, however, that this is a weakness in the current state of architecture rather than of Mr. Esposito's work. The truth is we are all trying to work this out together, and we are currently only mid-stream in our journey toward mature application architectures.

"Architecting Applications for the Enterprise" fortunately brings us all to the same point, as software professionals, and allows us to see the horizon for our collective next step forward.
22 von 24 Kunden fanden die folgende Rezension hilfreich
HASH(0x9d47151c) von 5 Sternen Value Issue 17. Mai 2012
Von Amazon Customer - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
The content of this book is quite good and very helpful. I want to warn anyone looking to buy this book that it is completely free on the Internet.

(To find it, just do a Google search on "Parallel Aggregation". It's the first site returned.)

So if you want to save money and not feel fleeced (as I did), then I would suggest the Internet version.
7 von 7 Kunden fanden die folgende Rezension hilfreich
HASH(0x9d4717f8) von 5 Sternen Gets better... 3. April 2010
Von S. Thompson - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
This book is divided into two halves - Principles and System Design. The first half of this book is like a computer science course in system analysis and design. In my opinion fairly boring really, unless you are completely new to the subject. It does create a context for the rest of the book and though and even though it was a bit of a chore, I did find some interesting tidbits of information in part 1. The second half of the book moves from the theory of architecting software into the implementation with comprehensive coverage of all the different logical tiers of a system - presentation, service, business and data. It also discusses the different architectures that can be applied depending on the technologies used (forms, web, ria ect). This is where this book really shines. For me the further I got into the book the more I liked it. The writing style is conversational which make this book an easy read, although occasionally the author loses the plot a little, taking half a page to cover a point that could be covered succinctly in one line or two line.

By the end of this book I kind of liked it, although having said that it doesn't really offer anything new that hasn't been covered in other books, apart from the fact that the focus is on .Net technologies. For me I don't think this book offers too much to experienced developers, especially those with a lot of experience using .Net. Also for general software architectural principals there are better books around. Being fairly new to the .Net framework I brought this book primarily for an overview of .Net technologies that could be used in architecting applications and the best practices in applying them. In that sense this book is pretty good.

So if you're new to architecting software, or want an overview of .Net technologies and frameworks read this book. For experienced .Net folks I wouldn't bother, as this book probably won't teach you too much, except perhaps maybe providing a different perspective on software development.

In summary, the first half of this book (principals of software development) I'd rate as 2 stars, the second half (system design), 4 stars.
Waren diese Rezensionen hilfreich? Wir wollen von Ihnen hören.