> The basic reason is that it fits a vendor & technology view. There > are few things easier in this day and age in taking a database and > lobbing up a website and doing some CRUD.
Agreed, sure isn't that what REST is all about (j/k) :) > This makes it very easy to dust off the EJB books and the PL/SQL > books and re-write them as SOA changing only a few works and a > couple of technologies. I'm worried thats bang on. As you know it was exactly the same in object land until relatively recently. It also seems like SOA authors don't seem to have learned the lessons, one of which is that focussing solely (or primarily) on data doesn't get you very far especially if what you want is an elegant and adaptable system. > If you are flogging some technology then it makes sense to base > anything you write about around the technologies that you have, and > it makes no sense at all to highlight that its actually the > intellectual model that matters. Makes sense, do you see this changing though? I ask because other than the next X installments of the Erl series and a few SOA patterns books I'm not seeing a lot of new content on SOA hitting the bookshelves. I'll definitely read your InfoQ book but I wondered if you'd thought of other approaches such as getting a blog network of like minded SOA practitioners together. Or do you think that things are already progressing nicely? -Colin Jack
