• Tous les prix incluent la TVA.
Il ne reste plus que 7 exemplaire(s) en stock (d'autres exemplaires sont en cours d'acheminement).
Expédié et vendu par Amazon. Emballage cadeau disponible.
+ EUR 2,99 (livraison en France métropolitaine)
D'occasion: Comme neuf | Détails
Vendu par SuperBookDeals..
État: D'occasion: Comme neuf
Commentaire: Remboursement garanti à 100%. Etat neuf, expédition rapide sous 4 à 14 jours ouvrés. Plus d'un millions de clients servis. Service à la clientèle en Français.
Vous l'avez déjà ?
Repliez vers l'arrière Repliez vers l'avant
Ecoutez Lecture en cours... Interrompu   Vous écoutez un extrait de l'édition audio Audible
En savoir plus
Voir les 2 images

SOA Patters (Anglais) Broché – 15 novembre 2012

4,2 étoiles sur 5
5 étoiles
4 étoiles
3 étoiles
2 étoiles
1 étoile
4,2 étoiles sur 5 9 commentaires client

Voir les formats et éditions Masquer les autres formats et éditions
Prix Amazon
Neuf à partir de Occasion à partir de
"Veuillez réessayer"
EUR 49,41
EUR 33,66 EUR 32,46
Note: Cet article est éligible à la livraison en points de collecte. Détails
Récupérer votre colis où vous voulez quand vous voulez.
  • Choisissez parmi 17 000 points de collecte en France
  • Les membres du programme Amazon Premium bénéficient de livraison gratuites illimitées
Comment commander vers un point de collecte ?
  1. Trouvez votre point de collecte et ajoutez-le à votre carnet d’adresses
  2. Sélectionnez cette adresse lors de votre commande
Plus d’informations
click to open popover

Offres spéciales et liens associés

Descriptions du produit

SOA Patterns SOA-Service Oriented Architecture-has become the leading solution for complex, connected business systems. While it's easy to grasp the theory of SOA, implementing well-designed, practical SOA systems can be challenging. Developers and enterprise architects still face several challenges: knowing when a service has failed, creating reports when data is scattered, and integrating SOA and the UI. SOA... Full description

Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.

  • Apple
  • Android
  • Windows Phone
  • Android

Pour obtenir l'appli gratuite, saisissez votre numéro de téléphone mobile.

Détails sur le produit

Commentaires en ligne

Il n'y a pas encore de commentaires clients sur Amazon.fr
5 étoiles
4 étoiles
3 étoiles
2 étoiles
1 étoile

Commentaires client les plus utiles sur Amazon.com (beta)

Amazon.com: 4.2 étoiles sur 5 9 commentaires
5 internautes sur 5 ont trouvé ce commentaire utile 
4.0 étoiles sur 5 Helpful introduction into SOA patterns 28 juillet 2014
Par Timmy_A - Publié sur Amazon.com
Format: Broché Achat vérifié
SOA Patterns is just second book I have read about SOA. The first one was SOA with .NET written by about 10 authors led by Thomas Erl. The book was complete disappointment. 800 pages of useless figures without any practical value (besides filling more space) accompanied with hundreds of pages of appendices repeating the same that was mentioned in previous chapters. The usefulness of that book was close to zero. Fortunately this was not the case with SOA Patterns. Just 250 pages is filled with much more and really useful information. Figures are practical addition to the text, not just to bloat the size of book.

As a SW developer who participated on just 2 or 3 SOA projects in very small teams without any SOA specialist I can say that the book helped me to consolidate my knowledge about SOA principles. Sure, many patterns are not so hard to figure out by yourself but still it's useful to have a confirmation from an expert that you are going the right way.

The thing that I really appreciate is the structure how the patterns are presented. The author divided discussion of every pattern into several topics: Problem, key question that describes the problem, solution with key 1-2 sentences long statement that gives you general view how solution will work followed be detailed description, technology mapping and quality attributes that pattern is trying to solve. Such division makes the text easy to follow. Another great thing was chapter about antipatterns. There are just 4 of them, but during my work for my employee I hit to all of them. This chapter was probably the most useful part of the book.

Even the book is good there are some things that can be improved. One thing that I miss is something like pattern summary - 2-3 pages that would summarize all patterns in 2-3 sentences. Many times I had to browse through the book to remind what referred pattern is trying to solve. Another problem was section called Technology mapping. Many times it was too generic without giving more details to actual technologies that can help you to implement related pattern.

To summarize - SOA Patterns is very practical and useful book that I recommend to everyone. Even experienced developers could benefit especially from chapter about antipatterns. And if you are .NET developer I also recommend Programming WCF Services: Mastering WCF and the Azure AppFabric Service Bus by Juval Lowy which is the book primarily for developers but containing many helpful advices how to desing your services in SOA way.
12 internautes sur 18 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 A Must Read for Every Software Architect 1 octobre 2012
Par T Anderson - Publié sur Amazon.com
Format: Broché Achat vérifié
I have been waiting for this book for a long time, so the first thing I would like to do is thank Aya, the author's wife. In the acknowledgements the author thanks her for making him man up and finish the book. The second thing I would like to do is thank the author for listening. A project like this had to have been difficult to finish.

The wait was definitely worth it. This is an excellent compilation of rock solid architectural advice. Having it delivered in the format of patterns is icing on the cake.

The book is broken down into two parts. The first part introduces SOA and then covers the patterns. The second part discusses SOA in the real world. I have listed the chapters and the patterns they include below. At the end of each chapter there is also a Summary and Further reading section which I do not show below.

Part 1 SOA patterns

Chapter 1 Solving SOA pains with patterns
Defining software architecture
Service-oriented architecture
Solving SOA challenges with patterns

Chapter 2 Foundation structural patterns
Service Host pattern
Active Service pattern
Transactional Service pattern
Workflodize pattern
Edge Component pattern

Chapter 3 Patterns for performance, scalability, and availability
Decoupled Invocation pattern
Parallel Pipelines pattern
Gridable Service pattern
Service Instance pattern
Virtual Endpoint pattern
Service Watchdog pattern

Chapter 4 Security and manageability patterns
Secured Message pattern
Secured Infrastructure pattern
Service Firewall pattern
Identity Provider pattern
Service Monitor pattern

Chapter 5 Message exchange patterns
Request/Reply pattern
Request/Reaction pattern
Inversion of Communications pattern
Saga pattern

Chapter 6 Service consumer patterns
Reservation pattern
Composite Front End (Portal) pattern
Client/Server/Service pattern

Chapter 7 Service integration patterns
Service Bus pattern
Orchestration pattern
Aggregated Reporting pattern

Part 2 SOA in the real world

Chapter 8 Service antipatterns
Knot antipattern
Nanoservice antipattern
Transactional Integration antipattern
Same Old Way antipattern

Chapter 9 Putting it all together--a case study

Chapter 10 SOA vs. the world
SOA and the cloud
SOA and big data

So what makes this book different from other SOA Pattern books? My take on that is that this one is written by a software architect who is writing to software architects. Yes the book is also appropriate for developers, CIOs, project managers, and testers, but it really speaks to the software architect.

The last section of every pattern description contains a quality attributes section. The author calls the patterns a solution and the quality attributes the requirements. Software architecture is all about the quality attributes. They are what help define the scenarios and the trade-offs that need to be made during architectural design. The quality attributes section maps the quality attribute to concrete attributes to a sample scenario. It really helps to highlight the architectural importance of the pattern.

If you have never read any of the author's published material, you should also take the time to check that out. His material on software architecture is great. He put together the SPAMMED architecture framework (SAF) which is a set activities that an architect can follow when they design an architecture. If you are not experienced with quality attributes, the author's SAF is a great place to start.

Another thing that I really like is that the author includes a technology mapping section with each pattern. Although an architecture can be designed out the specific technology in mind, I usually find that ignoring the technology often leads to an architecture design that isn't specific enough to actually be used.

It is also rare and unrealistic to think that you're going to be designing an architecture for an unknown technology. I always know what the environment is that I am going to be implementing in, at least that's been my experience. There may be several technologies used in the same environment, like the mobile environment that I am currently architecting. I do know the environment includes C#, Java, Objective-C, and ASP.NET MVC. I am therefore placing constraints on the architecture based on the fact that all these languages will be used for certain parts of it.

One of the coolest parts of the book is the appendix 'From quality attributes to patterns'. The appendix first gives a very nice overview of what quality attributes are. It continues with the section that explains how quality attributes are matched with patterns. There is then a very large table of quality attributes which are mapped to concrete attributes, sample scenarios, relevant pattern, and the chapter but you can be found it.

The author's writing style makes this book very easy to read. Each pattern is very well explained and the author makes great use of UML diagrams and other visualizations.

If you're going to purchase just one SOA patterns book, you should make it this one. Every software architect should have this book on their shelf.
1 internautes sur 7 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 Awesome Book! You ought to get one. 15 janvier 2013
Par Ingolf - Publié sur Amazon.com
Format: Broché Achat vérifié
I really like this book. It is very well written and just what I was looking for. If you are looking for a good foundation about SOA and learn from the authors experience, this will be a good read for you too.
1 internautes sur 1 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 You're thinking of adopting SOA and want to know the best way to do it? You must read this book! 20 août 2014
Par Julien Bourdon - Publié sur Amazon.com
Format: Broché
This book is divided into two parts. In the first, the design patterns which are the most relevant for SOAs are inventoried. Each pattern is explained step by step in a very clear and organised structure. At the end of each chapter, the author gives directions to resources to deepen the understanding and explore the implementations of each pattern. In the second part, the use of these patterns in the real world is described as well as some anti-patterns often found in organizations trying to adopt SOAs.

Using pattens is sometimes difficult, explaining them is even harder, but Arnon Rotem-Gal-Oz does a really great job conveying their importance and implementation using examples from his experience as an architect. The structure found in each pattern explanantion makes it more than yet another book on SOA, it is a reference book that you will likely keep on your desk.
2 internautes sur 2 ont trouvé ce commentaire utile 
3.0 étoiles sur 5 Super obvious things, with too many words 7 juin 2015
Par Ajeet Ganga - Publié sur Amazon.com
Format: Broché
-1 star : I read too much time on this book before realizing, I am learning barely anything new.
-1 star : The book is very watered down version, which could have been easily condensed by few folds.

E.g. : Decoupled Invocation pattern : This entire pattern could be summed up as, "Use queue for request and response"

Also I found this part really wierd, that some of the most obvious knowledge was presented in complex language. At the end of the chapter you will go like, aha, that is what he is trying to say.

>> Virtual Endpoint Pattern
>> ...'The ideal solution is to run redundant instances of the service, but to have it still be accessible through one address, appearing as a single instance.

I have worked in only larger corporations, but it is very hard to imagine, neigh impossible, that anyone would run a service hardcoded to instance endpoint.
Again the chapter/pattern IMO could be summed up as "Use VIPs please."

I have similar observation on most of the chapters, so I am going with assumption that the audience for the book is people who either think, "We have to meet with the Sr. Architect to decide on whether we should use VIPs or use IP addresses" or "Umm what is VIPs ?"

I also agree that there is a third possibility that, I have no clue what Author is talking about and so this book is not for me anyways ....
Ces commentaires ont-ils été utiles ? Dites-le-nous

Où en sont vos commandes ?

Livraison et retours

Besoin d'aide ?