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] Fwd: The Hidden Dividends of Microservices - ACM Queue


Hi Martin,

 

I thought the part about ”Warning Signs” did a decent job on the why “it’s not for everyone” aspect and (albeit somewhat less so) the various organizational and cultural implications noted (true, scattered throughout) addressed “the path to successful use is difficult” … but I don’t mean to be argumentative … it was a somewhat casual article.

 

I’d love to join the TC calls … always have them on my calendar with the intention of doing so … always have conflicting sponsor or MITRE events that have to take priority! L+J (need a smiley for “bittersweet” or something like that) … will keep trying.

 

Avanti,

BobN

 

From: Martin F Smith, BFC Consulting [mailto:bfc.mclean@gmail.com]
Sent: Friday, August 19, 2016 11:11 AM
To: Natale, Bob <RNATALE@mitre.org>
Cc: soa-rm@lists.oasis-open.org
Subject: Re: [soa-rm] Fwd: The Hidden Dividends of Microservices - ACM Queue

 

Bob--Sure, I wasn't trying to judge MS completely based on this short write-up and I get it that the author was focused on what he sees as the potential workgroup-effectiveness benefits of the MS approach. I was hoping he might expand on what he meant by saying "it's not for everyone" and "the path to successful use is difficult" but he did not.  Anyhow, why don't you join the next TC call if Ken can put a little time for discussion of this article and your perspective on the agenda?

Thanks,

 

Martin

 

On 8/19/2016 10:55 AM, Natale, Bob wrote:

Thanks, Martin … I thought the article was pretty good … the author can (IMHO) be considered an authoritative source in this wrt how the hyperscale cloud service providers are creating the de facto standard model for microservice architecture.

 

The article assumes that readers already understand that a microservice is a packaging construct for a substantive and separable chunk of business functionality exposed via an API-based service interface and corresponding SLA.

 

Supporting observations from http://thenewstack.io/succeed-failure-microservices/

 

Microservices architecture is the biggest misnomer since global warming,” Reinhardt said. “‘Global warming’ rolls off the tongue so much better than ‘climate change.’ The drawback is that every time you have a cold winter’s day, people say global warming doesn’t exist, whereas climate change just says that the frequency of weather events is more extreme. It’s the same with microservices: people by instinct immediately focus on the micro part.


But microservices architecture is an architectural approach that takes into consideration the way we work and the way we organize.

- - - - -

One tangential take-away from the ACM article that was a light-bulb moment for me was:

“The effectiveness of a set of tests can be measured less by their rate of problem detection and more by the rate of change that they enable.”

 

Avanti,

BobN

 

From: soa-rm@lists.oasis-open.org [mailto:soa-rm@lists.oasis-open.org] On Behalf Of BFC.McLean
Sent: Friday, August 19, 2016 9:33 AM
To: soa-rm@lists.oasis-open.org
Subject: [soa-rm] Fwd: The Hidden Dividends of Microservices - ACM Queue

 

I don't find this very convincing but it's short. <g>

One thing i noted is lack of indication that MS tied to use of containers. 


Sent from my iPad


Begin forwarded message:

From: Martin F Smith Sr <martinfsmith@cox.net>
Date: August 18, 2016 at 11:12:18 PM EDT
To: Martin F Smith <BFC.Mclean@gmail.com>
Subject: The Hidden Dividends of Microservices - ACM Queue

 



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