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

[rexbroo <rexb@starbourne.com>]

Yup,

My customer id <-> customer auth <-> customer creditcheck <-> customer order ensemble would work in a very similar, if not completely identical way. I'm not yet convinced that the API Gateway is necessary, and I think that if you can do without it, you should. Thinking heuristically.

Rex

On 2/16/2017 7:15 PM, Ken Laskey wrote:

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

-- 
Rex Brooks
Starbourne Communications Design
Email: rexb@starbourne.com
GeoAddress:
1361 Addison St. Apt. A
Berkeley, CA 94702
Phone: 510-898-0670