SOA-RA TC Conference Call, Wednesday, Nov 15,2006 s2

SOA-RM TC Conference Call, Wednesday, June 21, 2017

A: Administrivia

1. Roll call 2. Note taker appointed 3. Approve minutes from previous Conf Call 4. Review Actions B: Taskus Genuineus

5. Chair remarks 6. - Review meetings attended last week — Rex - NGINX Ask Anything — Ken - AWS Public Sector Summit - How does OASIS SOA Reference Model apply to MSA?

7. Review Committee Note procedures and templates

Link to Meeting Attendees Link to Meeting Notes Link to Meeting Actions

Meeting Attendees – Ken Laskey Rex Brooks Martin Smith

- Meeting Notes –

A – Administrative – Ken Laskey convened the meeting at 11:35AM ET, and chaired

1. Roll Call: Ken conducted roll call Quorum Achieved.

2. Note Taker Assigned: Rex Brooks

1 3. Approved Minutes for May 10, 2017. Rex made the motion and Martin seconded. All were in favor and none were opposed

4. Review Actions and Open Issues: Status Actions and Open Issues: - Martin: Update initial draft SOA-MSA side-by-side.—Martin posted a message to the TC list proposing a revised approach. Follow-up carried forward. - All: Review SOA-RM to identify potential areas for update.—Ken has started and will distribute initial review for discussion at next TC meeting. Update June 21, 2017: Ken noted that he has done some significant work on this and it will be exposed in our discussion. B – Taskus Genuineus

5. Chair remarks—Ken launched into discussions below rather than spending time on Chair remarks.

6. - Review meetings attended last week — Rex - NGINX Ask Anything - Rex reported that he missed this webinar but the recorded version is available and he took the action to write to their rep and ask for a link to the recording.. — Ken - AWS Public Sector Summit – Ken reported that this was sevnenth year they’ve done this and the first one was in a room with 50 people and this year they had 10,000 registered for it.

At the AWS Summit Ken spent his time in the track on DevOps where DevOp was defined as a collection of cultural philosophy, practices and tools to get rid of silos and encourage greater communication among key participants. Ken noted that Amazon’s own service software in 2001 was one monolith and now it is very decoupled so the change spoken about is reflected in the way Amazon’s services are assembled, developed and delievered.

One session in the DevOps Trace was titled “ATO in a Day”, where the discussion was about dramatically shrinking the time for US Government organizations to obtain ”Authorization To Operate (ATO)” for a system from months to weeks using the DevOps approach increasing velocity of development and delivery. Martin noted that merely declaring such a goal has significance for US Govern- ment agencies, since lengthy ATO processes effectively block implementation of the DevOps concept. Ken noted that with regard to including security within the DevOps model that testing needs to be done quickly, with maximum automation and often as part and parcel of the continuous development and delivery process.

2 Ken noted that the DevOps teams developing tools for developers were now using the practices of DevOps in their work mving forward. Ken noted that emphasis was placed on ‘capturing institutional knowledge as automated corporate knowledge and automated processes.’

He also noted that everybody was interested in AWS Lambda, Amazon’s “sever- less computing” offering in the Cloud environment. Lambsa relieves developers from having to be skilled at estimating and specifying hardware capacity specifi- cation needed to support their applications or services, allowing them to focus on application software development and continuous development/delivery. Ken cited the example of an application in which the uploading of a set of photos trig- gers an event that is sent to a function in in Lambda which launches, for example, a facial recognition processing action.

7. How does OASIS SOA Reference Model apply to MSA? Ken noted that in what he has looked at so far, in the SOA-RM one uses a service without having a private copy of it and basically accepts changes in the service as they are implemented by the service owner, but with microservices one retrieves a private copy of the service’s code and receives notice when there’s an update. Martin pointed out that this is a major point of distinction between SOA and MSA. He observed that in some ways the MSA approach of re-use by making private copies of code is similar to the pre-SOA practices of obtaining updates of language library code by getting a current copy to be installed locally.

Martin also noted that the RM doesn’t elaborate on re-use and doesn’t explain why re-use is desirable. Ken noted that there was some re-use mentioned, but it was not an emphasis. Martin noted that microservices revert almost to the concept of reuse of copies code blocks more than run-time use of shared services. He emphasized that microservices eliminate as many runtime dependencies as possible and thus improve performance and lower some types of risk, but do have a problem keeping updated in today’s high velocity development/delivery context.

However, as Ken noted, with microservices the process of update is also simplified. Ken said that with the microservices concept of “bounded context” the idea of getting a new image is acceptable but downloading say a whole Oracle™ database wouldn’t be. So quick exchange of microservices is doable as long as we keep the pieces small, but keeping up with large numbers of small pieces may present other challenges

Martin noted that the RM doesn’t provide guidance related to the notion of appropriate size of services (i.e., granularity) in SOA while microservices emphasize limited service scope (even in the term “microsevices”) .

8. Review Committee Note procedures and templates

3 Rex asked if it might be wise to elucidate where we think the RM could be updated. Ken asked if the notetakers from here on could capture bullet points to high- light these suggested changes/updates. That way we can keep track for the compi- lation in the document Adjournment The meeting was adjourned at 12:53 PM ET. Next meeting in 2 weeks—July 5, 2017. Bullet points for Committee Note: (Note: feature statements about microservices carry the implied question: How does this fit with the RM?)

 key implied question from earlier discussions: are microservices and Microservices Architecure (MSA) an extension of SOA?  in the SOA-RM one uses a service without having a private copy of it and basically accept changes as they occur, but with microservices one retrieves and uses a private copy of it and receives notice when there’s an update  the RM doesn’t elaborate on re-use  the RM cites re-use four times, but it is not an emphasized concept  Does SOA (vs earlier frameworks) result in greater economies by enabling re-use?  microservices eliminate as many runtime dependencies as possible and thus improve performance, but do have a problem keeping updated in today’s high velocity development/delivery  with microservices the process of update is simplified.  quick exchange of microservices is doable as long as we keep the pieces small.  Does SOA provide quality or security benefits by promoting "standard" and therefore lower-risk shared services?  Does SOA result in faster development?  Does SOA exploit the fact that it is now practical (thanks to the Internet and lots of bandwidth) to use non-local resources at run-time?  Does SOA provide a necessary governance (business, legal, etc.) frame- work (via concepts of service policy and description) for managing distrib- uted computing?

4 Actions carried forward – - Martin: Update initial draft template for side-by-side comparison of SOA vs. Microservices Architecture - Ken: Research and begin filling out OASIS Committee Note template - Ken: Circulate results of initial review of SOA-RM for potential update - - New Actions – - Rex: email link to NGINX Microservices Ask Me Anything: Part 3 webinar to TC email list

Parking Lot – - Peter: Complete a zip file for SOA-RAF UML Models and load to KAVI - Ken: Peter Brown/Ken finalize adjudication of comments received as a result of review of OASIS SOA-RM by IEEE. - All: Gather Statements of Use - Ken: Will coordinate with William as to when Ken can put discussion of his “patterns” write-up on the TC meeting agenda..