OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [soa-rm] Re: more on API Gateways


The offering sentence is my interpretation.  See the Example figure at http://microservices.io/patterns/microservices.html and the related text.

Ken

On Feb 16, 2017, at 10:09 PM, Martin F Smith, BFC Consulting <bfc.mclean@gmail.com> wrote:


On 2/16/2017 9:59 PM, Ken Laskey wrote:
each service knows the next service in the pipeline and choreography is used for control.

Umm . .  knows how? Control by what?  Sounds like a reference to another infrastructure tool for choreography.

Plus, this strongly suggest very close coordination among the developers of the MS that make up an app. On the one hand, that's not surprising in that MSA seems not to be aimed at re-use of a MS by multiple application or across enterprises. On the other hand, it seems to undercut one of the "principles" we ran across earlier, i.e., that MS lets each development team operate very independently. The statement above seems to imply a significant body of shared knowledge of the overall application and agreement on constraints imposed by the application's overall flow.

Martin





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]