SOA-RAF TC Conference Call,

Wednesday, December 21, 2016

A: Administrivia

1.  Roll call

2.  Note taker appointed

3.  Approve minutes from previous Conf Call

4.  Review Actions

B: Taskus Genuineus

5.  Red Hat MSA webinars

6.  Discussion -- Topics of interest to forward to RedHat

7.  Service granularity revisited

8.  SOA-MSA Side-by-Side

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:40AM ET, and chaired

1.  Roll Call: Ken conducted roll call

Quorum Achieved.

2.  Note Taker Assigned: Rex Brooks

3.  Approved Minutes for December 07, 2016 as drafted.

4.  Review Actions and Open Issues:

UML updates – remains open; Ken needs to get software

Incorporate IEEE review—Still open

Ontology and “patterns”—Message sent to Will Sweet requesting status

Ken contacted RedHat—He said he was asked for topics when he got the urls for the webinars. He said he was interested in use of data in MSA orchestration—Kubernetes deals with orchestration at the container level. Martin asked what is takng the place of ESBs wrt API Gateways and how stable is that functionality. Ken set an ACTION for group to look for topics to bring to Red Hat and bring them to the next meeting.

SOA/MSA side-by-side template --- Martin still working on it, probably will get more done after holidays.

5.  Red Hat MSA webinars. Ken reviewed his take on the webinars specifically as concerned data store management. He thought they will very useful description of the pieces of the MSA, a lot of which refer back to Red hat tools. He thought they were a little short on how those things actually work.

And he wants to gather topics for returning to Red hat with for future webinars.

6.  Discussion – Topics to forward to Red Hat. Martin asked if there was enough stability in how the various functions are needed to develop and run an application to even ask questions such as where does orchestration happen? Is it still a mishmash? Where is Discovery happening? Where is data model consistency happening? Ken noted that there is an Open Container Initiative (OCI) https://www.opencontainers.org/ working to collect practices into standardized procedures such as how to communicate with a container and its contents. Martin asked if anyone knew of an OASIS TC looking into this. Ken took an action to contact Chet (TC Admin) about this and completed the action during the meeting. Martin asked also what’s in an API Gateway.

7.  Service Granularity revisited. Martin said he was interested developing heuristics for service scope, e.g. how many lines of code are in the service/application, rather than interface granularity. Ken said he was still looking for a definition of what is an application vs. a service. Martin suggested that an application provides a complete transaction to an end user while service provides some function to another service or application. Ken asked how is the credit part of a shopping cart application should be categorized and Martin said that the credit part is a service or, probably, a microservice..

Martin said we should continue the research and conversation on email about how to scope services and microservices. Martin liked the idea of algorithmically profiling a service by a minimum number of external instructions/calls that go outside your slowly expanding service/microservicebox that would mark an optimal scoping mechanism to decide between adopting a MSA v. SOA approach to solving a given problem set.

Ken reiterated that he would like our discussions to end up as a Committee Note.

8.  SOA-MSA Side-by-Side—Rex suggested that Martin might want to include the single responsibility principle under MSA, e.g. Gather together those things that change for the same reason, and separate those things that change for different reasons.

9.  Adjournment

Ken moved to adjourn the meeting, Martin seconded.

The meeting was adjourned at 11:30 PM ET. Next meeting in 2 weeks—Jan 4.

-  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: Update initial draft template for side-by-side comparison of SOA vs. Microservices Architecture

-  Ken: Try to schedule RH rep participation in early upcoming TC meeting to discuss their view of MSA

- 

-  New Actions –

-  Ken: Contact TC Admin Chet Ensign to ask if there is an OASIS TC looking into Microservices and Containers—Action completed during meeting.

-  All: Group to look for topics to bring to Red Hat and bring them to the next meeting or send in email to TC list.

- 

3