Re: RE: [soa-rm] Fwd: The Hidden Dividends of Microservices - ACM Queue

["Mike Poulin" <mpoulin@usa.com>]

Hi Bob,

 

"a microservice is a packaging construct for a substantive and separable chunk of business functionality" - this is where a big devil is hiding!... This text substitudes existing with ddesirable. The correct statement is: a microservice is a packaging construct for a substantive and separable chunk of INTERFACES.  No one API defines any business functionality, it only names something that can be anything in reality. The owner and provider of the API has no reponsibility to the consumer for what is going on behaind the API. In the contrast, the SOA RAF makes Service Description and Service Contracts the 1st class citizens and API - the 2nd class. The Service Description and Service Contracts describe, declare and _promise_ certain business functionality to the consumer while the APIs are only the means of programmatic accessibility of the working body that provides/delivers promised functionality. 

 

While this seems an unimportant academic neuance, a lot of companies and consumers faild becuase of this. 

 

I have not (!) found a bit of a new value that microservices bring over a combination of Web Services (API) and EJB (container-related packaging of API). The latter was the only enterprise-level components in the pre-Web era. Microservices themselves (as well as Web Services) so not provide orientation on service.

 

Regards,

- Michael Poulin

 

Sent: Friday, August 19, 2016 at 3:55 PM
From: "Natale, Bob" <RNATALE@mitre.org>
To: "BFC.McLean" <bfc.mclean@gmail.com>
Cc: "soa-rm@lists.oasis-open.org" <soa-rm@lists.oasis-open.org>
Subject: RE: [soa-rm] Fwd: The Hidden Dividends of Microservices - ACM Queue

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

http://queue.acm.org/detail.cfm?id=2956643


Sent from my iPad