Arnon Rotem-Gal-Oz, Author of Manning's SOA Patterns, Shares a Free Chapter

DZone 's Guide to

Arnon Rotem-Gal-Oz, Author of Manning's SOA Patterns, Shares a Free Chapter

· Integration Zone ·
Free Resource

Here is an interview with Arnon Rotem-Gal-Oz, author of Manning's SOA Patterns, which is an under development book and currently available as an early access release.

You can participate in the discussion with the author by posting question or comment related to the book and win an Ebook or MEAP of the same title. One of participant will be given the ebook or MEAP.

A description of the book taken from the Manning web site is as follow:

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 a difficult challenge. Developers and enterprise architects still face the following issues:

  • How to get high-availability with SOA
  • How to know a service has failed
  • How to create reports when data is scattered within multiple services
  • How to increase the loose coupling of your SOA
  • How to solve authentication and authorization for service consumers--internal and external
  • How to integrate SOA and the UI
  • How to avoid common SOA pitfalls
  • How to choose technologies that increase the performance of your services

In SOA Patterns, author Arnon Rotem-Gal-Oz provides detailed, technology-neutral solutions to these challenges, and many others. This book provides architectural guidance through patterns and anti-patterns. It shows you how to build real SOA services that feature flexibility, availability, and scalability. Through an extensive set of patterns, this book identifies the major SOA pressure points and provides reusable techniques to address them. Each pattern pairs the classic Problem/Solution format with a unique technology map, showing where specific solutions fit into the general pattern.

SOA Patterns shows you how to address common SOA concerns, including the areas of performance, availability, scalability, security, management, service interaction, user interface interaction, and service aggregation. The SOA anti-patterns part shows you how to avoid common mistakes and how to refactor broken systems. The book also maps quality attributes to patterns so that you can easily find the patterns relevant to your problems.

The book content of the book according to the publisher is as follow:

  • Details more than 30 patterns for common SOA scenarios in the areas of security, performace, availability, UI integration, service aggregation and service interaction
  • Describes more than 20 SOA pitfalls to avoid
  • Spotlights the architecural perspective on SOA
  • Explains technology mapping from conceptual solution to current technologies
  • Provides extensive and practical advice on matching patterns to technologies

Here are some questions that we asked from Arnon and his answers which may help other people to get better understanding of the book writing process and the SOA patterns book itself.

-Please tell us something about yourselves. Who you are, where you are located, and what kind of work do you do?

I currently work as the VP R&D for a startup called xsights (www.xsights.com ). We are building a very cool visual search platform. Where in "Visual Search" I mean that you can take a picture of something, send it to us, we understand it and provide you with additional information. Before that I spent quite a few years as manager and architect building large distributed systems and SOAs in various verticals like defense, telecom etc.

-I see that you have a upcoming book "SOA Patterns". Is this your first book?

Yup. I actually didn't plan on writing a book. It started as a few blog posts (I blog on www.rgoarchitects.com/nblog ) and then I saw I have quite a few patterns to talk about. I posted a question if anyone would be interested in reading a book by me on the subject. One of the first replies I got was from manning and here we are

-What's this new book about?

Well, the book is about architectural solutions for common problems in distributed systems in general and SOAs in particular. I try to take a look at the different aspects of SOAs (like Security, Performance, Integration etc.) and synthesize my experience in solving specific issues in these areas. When I say "architectural solutions" I mean that what I offer are blue prints that can be implemented in different ways using all kinds of technologies. Indeed, I try to provide some technology mappings (mostly in .Net and Java) that show either uses of the patterns or ways to implement them. I also try to take a look at system quality attributes that are affected by the pattern in order to provide a more complete picture of each pattern.

-Who is your target audience?

I would say that the target audience includes anyone who is developing or designing Service Oriented systems and architectures.

-How long did it take you to write this book?

I am still writing it. I had quite a hiatus as I began my current job. However I've recently reinitiated my writing.

-What tips would you give someone who wants to write a book related to SOA and architecture?

I like this quote from Winston Churchill (via Ted Neward ) "Writing a book is an adventure. To begin with, it is a toy and an amusement; then it becomes a mistress, and then it becomes a master, and then a tyrant. The last phase is that just as you are about to be reconciled to your servitude, you kill the monster, and fling him out to the public."

-Are there other books that you'd like to write or are planning to write?

I was planning to write something about architecture in general or architecture in agile projects. However writing a book takes so much energy, I am not sure when I'll be ready to take such a commitment again.

-Which part(s) or chapter(s) of the you like the most?

I think I like most the first version of the first chapter (You can find it here ). The problem with it was that it wasn't aligned well with the other chapters but I think it can almost stand on its own.

-Is there anythig else which you like to tell the readers?

Also, I am currently writing the "anti-patterns" part (things that can go wrong) and this part seems to be more fun to write

You can download an early access edition of Chapter 2, Structural Patterns free of charge, you will only need to join Dzone's members family.


Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}