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: agenda for SOA-RM 20160217 (& things to think about)


Dial-in information will be sent to usual attendees and and other TC members who request it.

Agenda: 
- update of Wikipedia article on RM and possible RAF article
- fine and coarse-grained: how to characterize service and interface granularity.  
  . See minutes from 20 January meeting.  In particular, consider the following:
    .. the starting point for any attempt to develop guidance in this area should be to identify what decisions (by developers, users, services funders, architecture boards) would be informed by the guidance.
    .. summarizing goals: (a) easy to maintain; (d) easy to understand; (c) accommodate reasonable variability; (d) appropriate level of abstraction to limit number of separate services, e.g. zip code as parameter rather than each a separate service.
  . Other material to consider:
    .. previous emails with subject “following the discussion on interface granularity”.  In particularly, see Michael’s 12/10 questions and comments and Ken's 12/21 response.  
    .. also continue looking at “granularity ideas per 14 Oct to 9 Dec meetings” document uploaded to Kavi.

Also, for your entertainment, I found this YouTube (https://www.youtube.com/watch?v=wgdBVIX9ifA) from Martin Fowler on microservices.  Interesting point were:
- he consider microservices as a subset of SOA, not outside it
- an example he cites from others is Unix command line where have very small chunks of functionality to can pipe together
- and for a bit of humor, ESB = Egregious Spaghetti Box

I have been taking part in the SOA and Agility discussions at The Open Group, and they believe you can’t use microservices if a service has a dependency on another service, and so microservices can’t be used unless each microservice is a “world unto itself” (my words that were quickly agreed on).  I think some of this more to think about :-)

Talk with you on Wednesday.

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



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