Let’s get a few things straight. If you think the idea of using services as building blocks for your software is the best thing since 30″ displays and free schwag, then you already know this book exists. You also know that SOA is some serious stuff best left for trade magazines looking to sell more ads. Out there in the real world, we can’t get anything done without our power tools. And you heard of the one called REST, they say it’s the best brand around. So anyway, you already decided to read this book, now you just need to make it happen.
On the other hand, maybe someone handed you down SOA as a checkbox CEO feature for the next release. Well, why not use this opportunity to acquaint yourself with the difference between Web services and RPC calls. You’ll be glad you did when you have to come back and use the service you built. You could, perhaps, have a read.
If that’s not a subliminal message, I don’t know what is.
Caveat. To the exclusion of HTML5 — nice idea, but years off — this book focuses on things you can do right now. So obviously it’s loaded with Ruby and some Python code. Fear not, you don’t need to know either language to understand the sample code. What about Java shops? Well, there’s already a JCP in motion to bridge the gap and bring some of that goodness over, and I have to say it’s shaping to be a good one. But JCPs are not known for breaking speed records. I would suggest that you read the book very very slowly.
I won’t tell you anything else about the book, there’s no point for me to spoil the plot. But the good ones win in the end.
Disclosure. This is an affiliate link, I’m making money, you’re getting wise, that kind of deal. But I really don’t care how you end up reading it, just that you don’t miss on something important. And it’s the only book review I wrote this year (though, almost the only book I read), and I think that says something.