Understood. Money is made through obfuscation. We will provide clarity and let the chips fall where they may.
From: Mike Poulin [mailto:]
Sent: Monday, September 21, 2015 2:38 PM
To: Sweet Jr., William H <>
Cc: Rex Brooks <>;
Subject: Re: RE: [soa-rm] about PoSO and Microservices
Thank you, William.
I am afraid, the industry does not want any help becuase it makes money of this “reinventing the wheel” and this is not for the firat time. I would be happy if they just stop
refer to and compare with SOA.
- Michael
Sent: Monday, September 21, 2015 at 1:20 PM
From: "Sweet Jr., William H" <>
To: "'Mike Poulin'" <>, "Rex Brooks" <>
Cc: "" <>
Subject: RE: [soa-rm] about PoSO and Microservices
Very informative article! I am wondering how we can help the industry reach this level of specificity in understanding the relationship between SOA and
the various implementation “styles”. REST, ServiceComputing, Microservices and more are variations of SOA which are always susceptible to an interpretation which separates the variation from the main body of SOA work, resulting in “reinventing the wheel”.
To help the industry avoid this, perhaps we should include in our SOA ontology a subclass of SOA tentatively named Style or Variation, which is then specialized for each variation capturing what makes the variation unique. Perhaps this would help eliminate
some confusion currently found in discussions of variations.
William
From:
[mailto:]
On Behalf Of Mike Poulin
Sent: Sunday, September 20, 2015 7:26 AM
To: Rex Brooks <>
Cc:
Subject: [soa-rm] about PoSO and Microservices
Gents,
here is my short overview on how Microservices "compliant" with Principles of Service Orientation
Regards,
- Michael
