Re-imagining more from SOA (Panel Discussion)
•
1 recomendación•413 vistas
The document summarizes a panel discussion on reimagining SOA. It provides polls that were given to the audience on their understanding and adoption of SOA. The document discusses how SOA is an architectural pattern with implications across application architecture, information architecture, business architecture, technology architecture, and more. It also notes that while SOA is a powerful pattern, governance must be in place and managing SOA implementation becomes challenging.
Recomendados
Recomendados
Más contenido relacionado
Similar a Re-imagining more from SOA (Panel Discussion)
Similar a Re-imagining more from SOA (Panel Discussion) (20)
Más de Peter Carr
Más de Peter Carr (10)
Último
Último (20)
Re-imagining more from SOA (Panel Discussion)
- 2. Re-imagining more from SOA Panel Discussion
- 4. With implications in all disciplines GOVERNANCE M A N A G E M E N T D E V E L O P M E N T Application Architecture Information Architecture Business Architecture Technology Architecture SOA SOA
- 5. A pattern that can…
- 7. Where is innovation in today’s SOA? 1980 1990 2000 1970 EDI - 1975 Client Server - 1986 Mainstream Internet - 1994 XML - 1998 SOAP - 1999 Gartner SOA - 1996 WS-I BP - 2004 Technical Innovations Vendor Innovations Concept Innovation Business Innovations?
Notas del editor
- <number><number>
- Welcome and thank you. I’m Sam Higgins, Research Director with the local industry analyst firm Longhaus. As a taste of things to come after lunch when you’ll have to opportunity to attend some highly interactive breakout sessions I’m pleased to be your facilitator for what I know will be an informative panel discussion on re-imaging more from SOA. We’ll also be asking you some questions using your ILM terminals – so keep them at the ready.But before we begin lets re-cap on what we mean by SOA…
- Service-Oriented Architecture is not a stand alone concept. Indeed, the best way to think about SOA is as an architectural pattern. A pattern that supports the transformation of organisations to a service-oriented business model. A business model where the organisation views itself as a set of highly modular, but integrated services.As a result service-orientation starts with the business architecture with services specified in business context underpinned with in terms of contracts between the provider of that functionality and its consumers both within the organisation itself, but also between organisations.From this point the implications of SOA flow through the other dimensions of the enterprise adding a new spin on existing activities within each of the common architectural layers.Service oriented policies such as acceptable service levels and performance targets for the provision of business services.Service semantics that define the language and information required to effectively execute the services within the organisation.Implementation patterns to allow application developers to consistently create effective software services that align and support the business services.And finally software and hardware infrastructure that will support modern service-oriented deployment needs.While SOA is a powerful pattern there are implications the arise and should be kept in mind.<number>
- Implications for Governance practices, Development practices and Management practices.But when these understood then SOA offers significant benefits.<number>22/05/09Copyright 2006 Longhaus Pty Ltd - All Rights Reserved<number>
- The SOA pattern can increase the business impact of ICT investment such as…and Bring real opportunities for the CEO, CIO and CFO to better manage the ICT investments themselves through…It is these benefits that continues to drive organisations towards adoption of SOA. In 2007 Longhaus’ Enterprise Architecture Panel revealed that 80% of organisations were increasing their activities in relation to Business Process Management supported by SOA.A fellow research organisation, Springboard Research, found in their 2006 SOA study that less than 30% of organisation questioned the underlying benefits of SOA. This same study also revealed that 54% of Asia Pacific organisations were targeting re-use and interoperability benefits. IBM themselves recently reported that they invest over $1 billion US dollars annually in SOA have almost 6000 clients who have adopted their SOA offerings. Similar investments have been made all the major application software vendors.But ever silver lining has its clouds…
- Longhaus has observed two areas where organisations must ensure they stay focused.Firstly around managing the inevitable entry of SOA into the enterprise…Secondly, the “old school” cultural barriers around application ownership in a service-oriented world…<number>
- One of the criticisms of SOA is hype surrounding the concepts we’ve just discussed. Indeed, it sometimes seems SOA has been hanging around for quite sometime. A former author partner of mine, Paul Allen an analyst from Everware-CBDI, once wrote that for many SOA can sometimes feels like old wine in new bottles.Part of this sense of déjà vu comes from the history of SOA. In the 1970s EDI presented the earliest attempt at standardised message interoperability, while the advent of client-server provided the early foundations for distributed computing. But it was the advent of the internet and its implications for a wider network of online and interconnected businesses that lead two analysts, Roy Schulte and Yafim Natis, from Gartner to coin the term “Service-Oriented Architecture” (now you know why some people try to tell me SOA standards for Shame On Analysts).This really represented the first “SOA” innovation - a conceptual innovation. But this was shortly followed by technology innovations with the arrival of XML and then standard SOAP. The next wave of innovation around SOA was vendor-oriented SOA. That is, many vendors began to use SOA not just in custom engagements with clients, but within their own products and whole suites of interoperability standards were born to support vendor innovation.Now if like me then you have to ask yourself – if we’ve had three waves of SOA innovation, then where is the innovation in today’s SOA? Is it business innovation ? Or can we re-imagine more from SOA?To help shed some light on this question and on today’s use of SOA I’d like to welcome our panel and get them to introduce themselves to you.<number>
- <number>
- <number>
- <number>
- <number>
- <number>