PMC Minutes for 2010-01-06

Attendees

Rob Godfrey: JPM
Allan Beck: JPM

John O'Hara: Bank of America

Pranta Das: Cisco

Robert Greig: Barclays

Shawn MacAllister : Solace

Chuck Linton : Tervela

Colin McNaughton : Progress
Hiram Chirino : Progress

Andrea Moravec : DBS

Alexis Richardson : Rabbit

Dave Ingham : Microsoft

Matthew Arrott : TWIST

Mark Blair : Credit Suisse
Keith Owen : Credit Suisse
Roshan D'Mello : Credit Suisse

Carl Trieloff: RedHat
Gordon Sim: RedHat

Agenda

1: Participation update (John + Carl)
2: 1.0 PR2 update(Rob, Rafi, Laurie?)
3: Adoption to date (Carl)
4: Theme for 2010: Adoption Adoption Adoption… (John+All)
5: Conference date setting
6: Web site / AOB

Participation Updates

Contracts are in process of being amended and signing

AMQP 1-0

Will be prioritising the outstanding tasks

AR: We could use prototype to demonstrate management and wiring can be done through our APIs
In particular we can use the tools to create 0-8/0-9/0-10 wiring
RG: +1
JOH: +1
DI: +1 1-0 shouldn't be a backwards step in terms of functionality
Therefore we need the same management functionality (in terms of creating queues, create DTX)

ACTION: We should implementing this commonly in the working python prototype that we will be
implemented.

RG: We should be clear on how we can potentially accept third party contributions

AR: Where shall we host this?
Suggest github

GS: Does this mean that everyone is happy with the spec
AR: It means we have got as happy as we can get with just the document

MA: Will we be using Twisted?

RG: We may - although there is existing code which does not use Twisted

Adoption to Date

CT: Seeing considerable increase in demand around AMQP, and large and larger projects
Seeing other industries adopting AMQP
over .5 billion value bearing transactions per week
AR: 300-500 companies in production
Deployments of the order of 5000 machines
Only about 10% in finance
JOH: Strong desire to get SOA stack of TCP/IP<>AMQP<>JMS/WCF<->XML
We need to drive AMQP to be the dominant wire level protocol
RGr: Look at Google Insights around AMQP and messaging
I think we still have quite a lot of work to do
CT: Agree we still have a lot of work

Adoption

Discussion points:

• Protocol version consolidation

• Migration path from legacy wire protocols

• The advent of a credable default open SOA stack: TCP/IP + AMQP + JMS/WCF/? + XML + XML Schema + WSDL (amqp: transport)

• Integration with browsers

• Bringing the incumbants to the party

AR: Interoperability is key to adoption
We can interoperate on 0-9-1 between RabbitMQ, Qpid, OpenAMQ

RG: We can also translate from 0-9-1 to 0-10

JOH: We should break the relationship between the software and the wire protocol

RGr: There are a lot of corner cases that prevent easily exposing all features of legacy features through AMQP

JOH: Would like to see the common cases covered
have transparent proxies on the same system as the legacy broker
Have to have a way to allow people to gradually move off legacy systems.

MA: Bridging function between two clouds

Meeting closed 17:03 UTC