Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Image

Service Oriented Architecture With Java 110

Martijn de Boer writes "The book has been written to provide the reader with a short introduction to the concepts of Service Oriented Architecture with Java. The book covers the theory and analysis from the start and is progressing to a more intermediate level slowly throughout the different chapters. This book has been written for software architects and programmers of the Java language who have an interest in building software using SOA concepts in their applications. The cover hints to a series called “From Technologies to Solutions”, and that is exactly what this book tries to do, it tries to explain the SOA technology with different case studies and a path for solutions for your applications." Read below for the rest of Martijn's review.
Service Oriented Architecture with Java
author Binildas A. Christudas, Malhar Barai, Vincenzo Caselli
pages 192 pages
publisher Packt Publishing
rating 8/10
reviewer Martijn de Boer
ISBN 1847193218
summary This book is an overview of how to implement SOA using Java with the help of real-world examples. It briefly introduces the theory behind SOA and all the case studies are described from scratch.
When I ordered the copy of the book, I was under the impression that I was required some familiarity with terms used in the world of SOA but I was rather fond of the easy explanation of terms in the first chapter. The first chapter starts off with a small introduction to the role of software architecture when thinking about a software project. The chapter covers alternatives to SOA and tries to get the reader onto the right path for the rest of the book.

Later on in the book different subjects pass, the first few chapters start off with the basics of using XML as a communication layer. The third chapter introduces the audience to different implementations of web services in the Java world including the most familiar names as Apache Axis, Spring and XFire. The reader will be shown and guided to the install process of these web services and is being shown around the process of working with the software. The pros and cons of every piece of software are shown when following the steps throughout the chapters.

The book ends with chapters providing case studies of real world examples of SOA and alternatives. I have found this to be the most informative section of the book when looking to make decisions on how to architect a software project as it provides several examples on when to use which aspect of SOA. The different case studies allow you to put some weight and foundations into your decisions. The last chapter of the book is basically a conclusion of what we have learned throughout the book and provides a clear summary of goals of using service oriented architecture.

The reader is expected to have understanding of Java to follow the examples throughout the book. Examples are demonstrated on Windows machines, but could be followed on any other platform as well without having the hassle of setting up a different environment. That is one of the advantages of Service Oriented Architecture with Java, because it basically can be ran everywhere.

When you work your way throughout the book, you will discover different clearly illustrated diagrams and other informational graphics. There are more than enough images to make this something other than a boring theory book, as the images often provide a better understanding of different explanations of architecture and setups.

The book covers a small setup with Apache Axis 1.3 and mentions to use this opposed to the more recent 2.0 version because more software is being implemented on top of the 1.x series of said web service. However because the reader is starting to learn about SOA, it would have been great to see some of the differences and read why 2.0 hasn't been adopted much yet. I would have liked to see a bigger comparison between those two versions, but as the authors point out, there is a great community for both versions which provides a lot more background information if you want to look further into the more technical information that isn't provided in the book yet.

This book is a good way to get your feet wet in using web services to build and architect powerful Java applications for your business. I am no big Java developer yet, and I needed this book to navigate through the different pieces of software available, it succeeded very well at that point. I was fond of the clear writing style, which has always been the case by books from Packt Publishing. The book also has been written in a logical order, putting case studies at the end of the book so they are better to follow. Most technical books I own are written in a way that allows you to jump from chapter to chapter in an order that you need them, but I found this book to be a solid line of information of which the difficulty grade builds up from beginning to end. As a developer and software architect I really appreciate how well this book has been written for this audience, it's almost as if it was written especially for me and the knowledge I had of service oriented architecture.

You can purchase Service Oriented Architecture with Java from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

*

This discussion has been archived. No new comments can be posted.

Service Oriented Architecture With Java

Comments Filter:
  • Re:Java! (Score:3, Funny)

    by Icegryphon ( 715550 ) on Wednesday December 02, 2009 @02:42PM (#30300244)
    assembler is slow and useless, I write all my code in pure machine code.
  • by H0p313ss ( 811249 ) on Wednesday December 02, 2009 @02:45PM (#30300278)
    ... and actually write my proposed book: "Software Design With Popular Acronyms"
  • by discord5 ( 798235 ) on Wednesday December 02, 2009 @02:49PM (#30300348)

    In Dutch SOA stands for "Sexueel Overdraagbare Aandoening", or Sexually Transmitted Disease. Someone at my office recently received the prestigious title "SOA Expert", which of course has led to very strange looks from the mailman when a package arrives for him.

    It's been several months, and the joke still hasn't gotten old, which shows either the level of inappropriateness of the title in Dutch or the maturity of the people making the joke. (I'm guessing the combination of both)

  • TTL (Score:3, Funny)

    by MillionthMonkey ( 240664 ) on Wednesday December 02, 2009 @03:47PM (#30301072)
    What a bunch of babies everybody is. We implementing method calls in XML over HTTP from server to server as if they're pretending to be frigging browsers to each other. Remember when the world was simpler and we were using CORBA for that stuff? Or when we were going down to the TCP/IP layer and using sockets, and figuring our own stuff out? Before TCP we were sending raw IP packets. Uphill. Both ways. And it was good enough for us. We weren't kids anymore, writing BASIC programs on our little 8 bit machines. Of course BASIC was way too slow and you really had to go down to the machine code level to write anything that wouldn't embarrass you in front of your little friends. Really, all this stuff is based on a protocol that everybody should be using: TTL. And transistor-transistor logic should be good enough for anybody. If you can't rewrite your goofy SOA application using TTL it just shows how ignorant you are about what you're really doing.
  • Re:Java! (Score:1, Funny)

    by Anonymous Coward on Wednesday December 02, 2009 @09:36PM (#30306376)

    Java is fat and gay.

  • by binarylarry ( 1338699 ) on Thursday December 03, 2009 @02:24AM (#30307962)

    Uh, you forgot the last line of your post:

    "Get off my lawn, you damn kids and your rock and roll music, social equality and your high level programming languages!"

THEGODDESSOFTHENETHASTWISTINGFINGERSANDHERVOICEISLIKEAJAVELININTHENIGHTDUDE

Working...