Re: a pity conclusion

I think we had the vision but we didn’t always elaborate on the enabling concepts. Others jumped in with ESBs and UDDI registries to fill the void, and those of us who saw these as more anti-patterns were overwhelmed by the middleware sales pitch. I think things like microservices and containers now provide (some of) the missing enablers. My gut feel is there are still missing pieces. However, the new generation are off rediscovering some of the things we knew (or at least expected) those ten years ago.

Ken

------------------------------------------------------------------------------
Dr. Kenneth Laskey
MITRE Corporation, M/S H330 phone: 703-983-7934
7515 Colshire Drive fax: 703-983-7996
McLean VA 22102-7508

On Oct 14, 2017, at 6:12 AM, Mike Poulin <mpoulin@usa.com> wrote:

Hi Folks,

I am coming to conclusion that our SOA RAF came ahead of time for about 10 years...
Only now practitioners started thinking about applications that use our SOA Services. They call them "serverless apps" because these aps are external aps not controlled by developers. For the developers, it is an extraordinary situation (caused by Clouds business ownership, which I wrote about 2009) - they do not have access to the server/service-provider code. Absurd, but this is the reality. Below, is one of the articles about this - kids going to the primary school from a kindergarten and found a hell of the world outside. - Boring.

http://searchmicroservices.techtarget.com/tip/Experts-discuss-trending-serverless-apps-at-JavaOne?utm_medium=EM&asrc=EM_NLN_83952573&utm_campaign=20171013_Four%20classic%20DevOps%20mistakes&utm_source=NLN&track=NL-1806&ad=917084&src="">

Regards,

- Michael

soa-rm message