Ver 12 page 10:
“which is no more then about five minutes of downtime per
Year”
suggest:
“which is no more than about five minutes of downtime per
Year”

ver 12 page 16, Table 1.4 row2 col 3:
“SOA is an architectural style
for distributed systems. Most
other styles don’t have a
“distributed mindshare” and
they disA paper I wrote
which explains how the
fallacies are still relevant
today”
It looks like some text has gone missing here….

ver 12, section 2.1, page 20:
“This pattern deals with the environment where service instances run, and it handles some of the basic tasks associated.”
Suggest:
“This pattern deals with the environment where service instances run and it handles some of the basic associated tasks.”

ver 12, section 2.1.3, page 22:
“…..They perform this magic through the use of the Dependency Injection pattern, which is a non-SOA pattern.”
Suggest (if my understanding is correct):
“…..They perform this magic through the use of Dependency Injection, which is a general pattern not specific to SOA.”

ver 12, section 2.1.3, page 23:
“It also helps flexibility as you can easily change the implementation of the dependencies without affecting your code, as long as they keep their contract.”
Suggest:
“It also helps improve flexibility as you can easily change the implementation of the dependencies without affecting your code, as long as they keep their contract.”

Ver 12, section 2.1.4, page 23:
“The other quality attribute this pattern provides is portability, which is enhanced by the separation of concerns effect of the pattern, as was demonstrated in the scale-down example mentioned above.”
Suggest:
“The other quality attribute this pattern addresses is portability, which is enhanced by the separation of concerns implicit in the pattern, as was demonstrated in the scaled-down example mentioned above.

Ver 12, page 26:
“A thread in the edge component(s) is a good way to deal with contract-related temporal issues, such as timeouts events.”
Suggest:
“A thread in the edge component(s) is a good way to deal with contract-related temporal issues, such as timeout events.”

Ver 12, Fig 2.5:
“Cusomers” should be “Customers” for the <<service>> instance
“dicount” should be “discount” in diagram note

Ver 12, section 2.3.1, page 29
“Fortunately, things work most of the time, but as Murphy have it, our service is bound to fail eventually.”
Suggest:
“Fortunately, things work most of the time, but as Murphy would have it, our service is bound to fail eventually.”

Ver 12, page 30:
“….after step 2.1, where am order..”
Suggest:
“….after step 2.1, where an order..”

Ver 12, Figure 2.7, page 31:
The “End Point” component appears visually to be a “Pattern Component” when the Key is considered… however the “Contract” & “Service” are correctly presented.

Thanks
Arnon