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

SOA-RAF TC Conference Call, Wednesday, November 23, 2016

A: Administrivia

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

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

Meeting Attendees – Ken Laskey Rex Brooks Martin Smith Michael Poulin

- Meeting Notes –

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

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

2. Note Taker Assigned: Rex Brooks

3. Approved Minutes for November 9, 2016 as drafted. 4. Review Actions and Open Issues:

1 - Ken noted that we collected our questions for the Red Hat representstive, Jason Calloway, but he stopped responding so the action is CLOSED - Ken said he had lost track of the AWS item but that they are looking for government partners and looking for people to do quality work in the area. He said he found the discussion about AWS in the Intelligence Community interesting. CLOSED. - Ken noted again that he and Bob Natale spoke with a NGINX representative about Microservices and SOA based on article/book on SOA vs. Microservices on September 22—noting it was a good discussion. Ken will brief us on this at the next meeting once he can find his notes in the ongoing disruption of renovations at MITRE. CARRIED FORWARD. - Martin is reading through SOA Framework document to prepare for his side- by-side comparison between Microservices and SOA, and is think of taking goals and principles as the rows for the side-by-side comparison. 5. Microservices The TC continued discussion of microservices, with specific interest on the developmental aspects, e.g. small teams that focus on a microservice and stay with it instead of moving on to other things to enable continuous delivery. Michael wanted to focus on API in terms of who exposes it and how teams can use it as mechanism to connect reuseable microservices. Michael took a bank microservice API for withdrawing money from account as an example that other development teams can use without coordination. The problem is that microservices can get stuck waiting for operations to complete or risk problem of stale information synchronization of bank balance. We agreed that in this and many other instances, there can be problems. Ken noted that microservices are looking at an unlimited number of consumers that can scale horizontally, but this is not logical when multiple applications use a given microservice. Martin said that this is a problem for consumers who aren’t aware of update cycles for shared datastores or small changes in microservices due to continuous deployment. Rex suggested that our value might be in pointing out some of the pros and cons of the comparison between SOA and Microservices Architecture. Martin said his side-by-side comparison could work well for that. Ken noted that in the 2011 timeframe IEEE was looking at developing a SOA Reference Architecture. They became aware of work done in The Open Group and in the OASIS SOA RM Technical Committee. The IEEE decision was to propose that the work of the two groups be used as guidance for any IEEE SOA Reference Architecture. The efforts to adopt these bodies of work was never comp.eted. In the interim The Open Group submitted their work to ISO. After several years of comments and revisions some of which was contributed by representatives of this Technical Committee, the revised work became an ISO Standard this past Summer. In addition to the effort to use the OASIS and Open Group works as guidance the IEEE is looking at adopting the ISO Standard. The work is continuing along this path and this Technical Committee is involved.

2 6. New Business. Michael explained some of his latest work in developing his Concept of Orientation on Service (COS) and Ken noted that he had been certifiedas a SAFe Agilist from SAFe http://www.scaledagileframework.com/ and both of these topics will be scheduled for future meetings 7. Adjournment

Rex moved to adjourn the meeting, Michael seconded.

The meeting was adjourned at 12:56 PM ET. Next meeting in two weeks.

Actions carried forward – - 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. - All: Develop ideas for where we can focus to develop conclusions/guidance on use of microservices. - Martin: Develop first-draft template for side-by-side comparison of SOA vs. Microservices Architecture New Actions – -