The Author Online Book Forums are Moving

The Author Online Book Forums will soon redirect to Manning's liveBook and liveVideo. All book forum content will migrate to liveBook's discussion forum and all video forum content will migrate to liveVideo. Log in to liveBook or liveVideo with your Manning credentials to join the discussion!

Thank you for your engagement in the AoF over the years! We look forward to offering you a more enhanced forum experience.

DaTo (1) [Avatar] Offline
Dear author,

Here are some comments as I was reading the latest release. It's all suggestions of course, and errors are my own.

Typesetter has to go over this

- Quotation marks - they come in various styles.
- There are typos, which it is unfruitful to pursue here in detail
- p.9 contains a heading in an incorrect style
- Figure 2.5/2.7 has typo: "cusomers" instead of "customers"
- p 22. "ODBS" instead of "ODBC"
- Inversion of Control is abbrevioated "IoC" not "IOC"
- .NET is sometimes written ".net"

Bibliography formatting

The bibliographies on p.17 ff. etc probably need formatting, see for example: [where is the BibTeX of my student days ... ]

Synchronize titles

"Table of Contents", Chapter titles and Table 1.3 on p.15 probably have to be synchronized - the texts are diverging.

Unhappy diagrams

Figures 2.9 and 2.11 etc. are rather unclear. I can't make much sense of them. I suggest something like UML interaction diagrams to make the meaning clearer.


On p.20 - I never heard about the verb "workflodize". Where does it come from? [Maybe something for the references: the associated ideas that Dirk Koening uses in the Groovy context: "liquid heart" (flexible and often changed inner module called by outer modules) and "superglue" (flexible and often changed outer module calling inner modules) - see]

On p. 36 - "Saga" for long-running (compensating?) transactions. Never heard of it, but it seems to be just a "long-running,(compensating) transaction" (,

Transactional Service - ACID vs. BASE

Maybe an idea: Should one point the interested reader to "relaxed transaction" and the CAP theorem, in particular the February 2012 issue of IEEE Computer and the article "Overcoming CAP with Consistent Soft-State Replication"?

Edge Component Mystery

I'm still not 100% sure what the "Edge Component" pattern is about.

It nearly sounds as if the "Edge Component" is about modularizing out some aspects of processing and then arranging these modules through workflow logic. Thus is overlaps with "workflowdize".

But on p.45 one reads "In a sense the Edge Component pattern provides a fa├žade, or proxy, to a service implementation." In that case, it would something like a "gatekeeper pattern" doing precondition checks and filtering and anything to protect the "core".

Well, that's it for now.

Best regards,

-- David
arnonrgo (62) [Avatar] Offline
Re: Reading MEAP v1.4 up to chapter 2
Hello David,
A more updated version of the book (after tech proof etc.) has already been sent to production (i.e. it will now go through copy-editing, index etc). I did already fix a lot of typos in the proces (and rewrote some stuff) as well as updated the bibliography formatting.

Anyway regarding your other questions

Regarding the name Workflodize - I know that's not a real word but I applies the same form in "Productize" to wrokflow that's it. Sorry if you don't like that.

Regarding Saga
I think long-running transaction is not a good name as transaction implies locks and ACID in any event the term Saga comes from the data base world - as noted in the text it originated in this paper

ACID vs BASE - nice idea , if I can still make changes I'll add that to the further reading

Edge component is about separation of communications and the rest of the SOA stuf from the actual business logic

Thanks for your comments

Message was edited by: