Is it possible to get a job on oracle SOA? Hope you are giving a response to me..

best regards,
Suresh,

One of the best books which answers the question , Why Web Services?? Unique perspective on middlewares in general.

Do not expect any code examples or details of any particular middleware.
Rating: 5 / 5

Advice: if you are looking for a hands-on how-to book about XML this is not the book to pick up. Otherwise, if you are looking for a good fundamentals book that will help you paint a big picture of Web Services this book is great!
Rating: 5 / 5

This book is must have which draws detailed conceptual and architectural views on Distributed Systems, EAI and Web Services.

Rating: 5 / 5

I gave it 4 stars mainly because it kept me interested throughout AND Chapter 6 was well worth the wait. Also, the author was direct and decisive in what he was saying. I never felt while reading that he was talking over my head or down to me from some higher plateau.

Some criticisms which kept it from a perfect 5 include:

(a) Too many repeated themes. I felt at times that I was reading the same sentence and paragraph over and over. Not a major thing, but I think I read that XML is a “standard” for organizations to exchange business data more than twice!

(b) The author throws around many acronyms, some of which without expanding. At one point, he used “PO” to refer to “Purchase Order” and I really had to stop reading and thing about what on earth a PO was (duh!). There are several examples of this throughout the text making it a bit difficult to read.

(c) Related to (b), I would have liked to read more background on some of the technologies discussed. Examples include the Java technologies that the author refers to throughout. I’m not a Java developer, so I felt a little behind in some of the discussion.

(d) I think the author spent too much time on his low-level XML discussion. I realize that XML is integral to SOA but for a book designed for “architects” and “senior developers”, as the back cover suggests, it seemed too deep for “architects” to care about and too shallow for “senior developers”. It might have been better to present an XML primer and leave it at that.

(e) By reading this book, I DO NOT feel ready to build an SOA, nor do I feel qualified to jump into a team implementing SOA.

Chapter 1 was a sufficient setup for the chapters to come. It would have been good to build a better case for SOA, though. If I was on the fence about SOA, I don’t think this book would have convinced me that my organization needed to go down this path. This chapter does however provide a lot good background and helps draw the line between different integration strategies.

Chapter 2 introduces the ESB — which for me is the most interesting aspect of the SOA approach. There is also a good discussion about processes and orchestration, which was enlightening (coming from me, who has no real world SOA experience).

Chapter 3 was the lowlight. I found myself skipping ahead when the author started discussion XML schemas, namespaces, declarations, and the like. I know this stuff already and was wondering how an “architect” or “senior developer” (I’ve been called both) would treat this chapter. I concluded that they would do essentially what I did: skim it. It is too light to be a reference and too heavy to be of any practical value.

Chapter 4 was better than the previous chapter. I like history (IT Evolution, and WS Specifications) and discussions on Patterns (the author discusses integration patters, business patterns, composites, application patterns, and runtime patters). He does however loose me a bit on writing WSDL and the simple web service example. I’ve written several web services and understand the concepts so I found myself skipping ahead a bit.

Jaded by some of what I read in Chapters 3 and 4, Chapter 5 got me back in the mood. BPEL. Finally. The book had been talking about BPEL (Business Process Execution Language) on-and-off and now this chapter gave me a heavy dose. Good job.

Chapter 6 was my favorite chapter by far. ESB is an area of interest for me, and to have it explained and examined in the context of SOA was eye opening. In fact, it’s one of the reasons I wanted to read this book in the first place.

All-in-all, I learned a lot from this material. I took a few notes, which will lead to further research on my part. This book presents a good overview of some of the complexities and key points in building an SOA infrastructure/environment. Get it if that is what you’re looking for!

Rating: 4 / 5

Because of their experience with Packt Publishing and their real world experience for SOA, Packt has chosen them to write this book about SOA Integration.

Clearly this book requires deep familiarization of the components discussed in SOA. XML and Web Services are extensively discussed so that developers will understand why the mark-up language (XML) and approach (Web Services) is perfect for integration which eventually leads to SOA. For those who are beginning in SOA, this book provides explanation in great detail in the basic concepts of SOA – from the challenges until specific terms that will greatly influence in building an application using the architecture.

What is even interesting is that it provides an insight to an alternate to JavaEE and the .Net framework. If you have a vague idea of what COBRA is, then this book will enlighten you further why this application web language could help you in building an application.

Some parts of the book are great for beginners while other parts of book are intended for advanced users. If you are looking for specific instructions on how to integrate XML to SOA, then this book will help you. For beginners or for those who just wants an in depth information of SOA, then this book will also be of great assistance.

Ultimately, this is a great addition to your library as it provides the basics while introducing you to the advanced concepts and principles behind SOA.
Rating: 5 / 5

There are a set of standards that make all this possible, and the text explains these. The lowest level is simply to use XML for data interchange. This gets around the alternative of binary data interchange, and all the compatibility problems therein. The latter was the realm of CORBA. But that proved brittle in many practical deployments.

Another standard is the Web Services Description Language (WSDL). This and BPEL let you construct interoperable “parts”, that can usefully interact with other programs on the net.

There is lots of practical advice. Like the fact that parsing large XML documents can be slow. So you should not use XML to communicate between tightly coupled components. Plus, the book offers numerous patterns that can simplify your design efforts. These patterns have proved successful in existing applications, and you should take advantage of them whenever possible.
Rating: 4 / 5

Chapters:

1.) Integration Architecture, Principals, and Patterns – covers a wide variety of concepts including types of integration including data, application, process and presentation. It also speaks to layers of integration such as communications, brokering, routing, transformation and others. The authors touch on various technologies in the integration arena, for example, database access, message oriented middleware, remote procedure calls, transaction monitors and more. The chapter finishes up with a quick overview of the integration process, various practices activities and patterns.

2.) Service and Process-Oriented Architectures for Integration – talks a great deal about the concepts and standards that make up Service and Process Oriented Architecture. It is not an in-depth tutorial on either subject but is a good reference for the standards associated with them and why they are well suited for integration.

3.) Best Practices for Using XML for Integration – is closer to a tutorial on XML than a description of the architectural rationale and implications of it with respect to SOA. Since part of the target audience is developers the level of detail in this chapter is not un-warranted. This chapter includes a comparison of JAXP API’s and shows a number of XML schema and XSL stylesheet examples. It also speaks in reasonable detail to validation, security, encryption and performance considerations with respect to XML.

4.) SOA and Web Services Approach for Integration – steps more deeply into the area of web services and again much of it is directed to developers as opposed to architects. It contains a good overview of various patterns and contains some guidelines on their usage. The chapter contains a light review of web services for B2B and EAI and then a more detailed description and examples of interoperable web services, WSDL and WS-I.

5.) BPEL and the Process-Oriented Approach for Integration – speaks in more detail about BPEL and what the authors refer to as “the process-oriented approach to SOA-based integration.”. This chapter addresses the usual suspects of choreography, orchestration and complexity in a clear fashion. It then goes into more depth on writing BPEL processes and works through a fairly complete example.

6.) Service and Process-Oriented Approach to Integration Using Web Services – gets to the heart of the notion of using SOA for integration by delving into the Enterprise Service Bus (ESB). This chapter covers the ESB at the appropriate level of abstraction for an architect and touches on key areas such as mediation, transformations, communications, transactions and security.

Conclusion:

I enjoyed the book and felt it delivered on the topic of SOA Approach to Integration. Trying to target both architects and developers is a difficult task but readers from either area will find something useful in this book. It is not the definitive work on SOA and Integration but it does a good job of tying together a broad range of material and will be a welcome addition to anyone’s technical library.
Rating: 4 / 5