Re: RE: [soa-rm] about PoSO and Microservices

William,
your suggestion raises serious questions that are the cornerstones of many debates on this topic. Actually, there are two fundamental questions, IMO:

1) Where an Architecture ends and its Implementation starts?
- for this, I have a definition of an Architecture that many consider too restrictive (because it clearly surfaces fallacy claims of the architecture subject vs. discipline. E.g., ‘people’ is not an architectural element, though it is very important to the operations of a business/technology system)

2) What are the boundaries of service orientation? If a certain category of entities adheres to _only_ a few PoSO, not to all, may it be considered service-oriented and to be a Variation of SOA or this is a Variation of SOA Implementation (then, who cares!?..). What constitutes that we still deal with a Variation of SOA or ‘this’ is not SOA already?

- Michael

Sent: Tuesday, September 22, 2015 at 2:16 PM
From: "Natale, Bob" <RNATALE@mitre.org>
To: "Sweet Jr., William H" <wsweet@mitre.org>
Cc: "soa-rm@lists.oasis-open.org" <soa-rm@lists.oasis-open.org>
Subject: RE: [soa-rm] about PoSO and Microservices

Excellent advice, William. (Needs to be adopted in many other contexts by many other groups and individuals.)

Avanti,

BobN

From: soa-rm@lists.oasis-open.org [mailto:soa-rm@lists.oasis-open.org] On Behalf Of Sweet Jr., William H
Sent: Monday, September 21, 2015 8:21 AM
To: 'Mike Poulin' <mpoulin@usa.com>; Rex Brooks <rexb@starbourne.com>
Cc: soa-rm@lists.oasis-open.org
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: soa-rm@lists.oasis-open.org [mailto:soa-rm@lists.oasis-open.org] On Behalf Of Mike Poulin
Sent: Sunday, September 20, 2015 7:26 AM
To: Rex Brooks <rexb@starbourne.com>
Cc: soa-rm@lists.oasis-open.org
Subject: [soa-rm] about PoSO and Microservices

Gents,

here is my short overview on how Microservices "compliant" with Principles of Service Orientation

Regards,

- Michael

soa-rm message