SPA Conference session: Holistic enterprise XML messaging | |||
| One-line description: | Data standards, evolution, governance and architecture | ||
| Session format: | Case study (75 mins) [read about the different session types] | ||
| Abstract: | The case study gives account of the presenter’s experience in the design and implementation of enterprise XML messaging systems. It shows in particular how the evolution of the XML schemas that define the messaging data standard can not be addressed exclusively at the schema level, but also in the system architecture, in the design of the applications that produce and consume messages, and in the business process that stakeholders follow to propose and approve schema changes. A holistic approach that considers all the organisational and technical aspects of the messaging system is therefore required. The presenter will describe the case, the main problems encountered, and some best practices identified to tackle these issues. Best (and worst) practices include: - Definition of backwards forwards compatibility - Definition breaking and non-breaking changes - Definition of a governance process - Introduction of abstraction layers - Automatic code generation (worst practice) Objectives: see "benefits of participating" | ||
| Audience background: | The session is aimed at architects, designers, developers, and project managers with an interest in enterprise messaging systems. Some familiarity with XML technology and SOA is advantageous. | ||
| Benefits of participating: | Participants will... - gain an increased understanding of XML messaging systems and of the issues surrounding the design and evolution of a data standard. - learn that sometimes, contrary to expectation, a systems consisting of decoupled components, has to be designed in an integrated holistic way. - learn some best practices that they can integrate into their work. | ||
| Materials provided: | - Presentation slides, with annotations - A document summarising the case and the material covered in the session | ||
| Process: | The session will be run, at least in part, interactively. The participants will be divided in groups and during the course of the session invited to... - draw parallels between the case presented and their experiences - critique the practices described - consider if they could integrate practices in their work, which may or may not concern XML messaging | ||
| Detailed timetable: | 00:00-00:20 – Case study exposition 00:20-00:25 – Q&A 00:25-00:55 – Explain issues and best/worst practices 00:55-01:05 – Map case study and practices to participant’s experience 01:05-01:15 – Participants present lessons learned | ||
| Outputs: | - Papers and flipchart sheets of the concepts that each group has learned during the session | ||
| History: | New session. The material draws from the presenter’s experience in the design of XML schemas and XML-based messaging systems in the finance sector and from his academic research work in the area of XML schema evolution. | ||
| Presenters | |||
| 1. Daniel Dui Independent |
2. Anthony Coates Londata Limited |
3. | |