Soa In The Combat Zone
Download as PPT, PDF7 likes616 views
1) The document discusses best practices for successfully implementing a Service Oriented Architecture (SOA) for the first time. It emphasizes the importance of understanding business needs, defining clear ROI, and focusing on architecture before technology. 2) Common mistakes discussed include using the wrong people, selecting technology too early, not properly designing services, and not considering business needs or thinking strategically. 3) Key recommendations include having executive support and budgets, beginning with architecture, getting the right talent, defining incremental successes, and following a repeatable process from understanding the problem domain to selecting technology.
Soa In The Combat Zone
- 1. SOA in the Combat Zone How to Succeed with SOA the First Time, and Never Make a Mistake David S. Linthicum September , 2008 Building a Foundation for Continuous Change
- 2. Time to Make Something Work We’ve been working with the notion of SOA for over 5 years now . We’ve proven that SOA can work, if you approach it correctly. We need to start doing, but never stop learning. They hype is officially over. Time to make something work!
- 3. What went wrong? “ We could not get the culture to shift to accommodate the disruptive changes we needed for SOA.” - Name withheld upon request “ We put our trust into a single large vendor and our technology solution was not the right fit.” - “ Do not use my name” “ We service-enabled everything…now what?” - “I’m a complete idiot.”
- 4. What worked? “ We changed our leadership to change the culture to make way for new approaches, such as SOA.” “ We took the time to understand the business first, then the technology.” “ We focused on the architecture.” “ We made some quick wins which provided creditability, and built more complex and far reaching projects around that very positive foundation.” “ We created a common team across the organizations which broke down any political barriers.” “ We spent a hell of a lot of money.”
- 5. So, how do I win with SOA the first time? Make sure there are advocates with budgets, at the executive level. Begin with architecture, not with technology. Get the talent and knowledge you need now. Understand that SOA is ongoing (journey not a project). Focus on understanding the business. Define the ROI up front, and make sure it’s there upon delivery. Follow a repeatable process (later in this presentation). Build your SOA with the emerging Web in mind (WOA). Define incremental successes, and make sure to get there. Follow everything in this presentation.
- 6. Architecture is not About the Technology It’s about what you’re building, then how you build it. It’s about understanding first, then building.
- 7. SOA Challenges Source: Wipro
- 8. SOA Meta Model Data Abstraction Data Data Data Services Legacy Legacy Services Process/Orchestration/Composites Monitoring/Event Management Governance Rep Security Internet-Based Services New Services
- 9. 5 Things to Avoid Using the wrong people. Selecting the technology too early. Not considering “service design.” Not factoring in the business. Not thinking long term, and strategic.
- 10. Using the Wrong People Perhaps this is something you should not outsource. This is architecture, not development. This is strategic, not tactical. Existing talent may not be up to speed. You may love your current team, but perhaps they are not up for the job. Make the cuts now, not later. Don’t let consultants or vendors drive the project.
- 11. Selecting the Technology too Early Don’t “manage by magazine.” Don’t overuse “comfort vendors.” Avoid VDA (vendor driven architecture) Business -> Requirements -> Analysis -> Technology. Now repeat! Make sure to do a POC, and other testing. Never be afraid to toss out technology.
- 12. Not Considering “Service Design” Services are not applications. Services are not APIs. Services are services, and should be designed properly. Consider granularity. Consider repeatable design. Consider testing.
- 13. Not Factoring in the Business Always do ROI analysis before you begin work on your SOA. Understand core business processes, and what needs to improve. Understand core business drivers, and be able to sell them within the organization. Make sure business analysts have input at various stages.
- 14. Not Thinking Long Term, and Strategic SOA has a positive impact after years, not months. SOA is not a development project, it’s a journey. SOA requires a systemic change in how you do architecture, it’s not just an instance of an architecture. SOA requires long term corporate commitment to be successful.
- 15. Understand your business objectives and define success. ROI Define ROI Create Business Case Business Case
- 16. Define your problem domain System Descriptions System Complexity Analysis SOA POC POC Results Domain Descriptions Vendors
- 17. Understand all application semantics in your domain. SOA Metadata Meta data analysis Data abstraction layer definition Data Abstraction Layer Data services definition Data Services Legacy Metadata External Metadata (B2B)
- 18. Understand all services in your domain. Candidate Services Service analysis Metadata and services analysis Services And Information Performance analysis Services And Performance Legacy Services External Services (B2B) SOA Metadata
- 19. Understand all processes in your domain. Candidate Processes Process analysis. Define metadata, services, and processes Processes, Services, And Information Process integration analysis. Process Integration Diagrams Candidate Services External Processes (B2B) SOA Metadata
- 20. Define new services. Candidate Processes Service definition. Service design. Processes, Services, And Information Service implementation. Process Integration Diagrams SOA Metadata Candidate Services Service Definition Service Design Service Implementation
- 21. Define new processes. Candidate Processes Process definition. Process design. Processes, Services, And Information Process implementation. Process Integration Diagrams Metadata Candidate Services Process Definition Process Design Process Implementation
- 22. Select your technology set. Technology Requirements Define requirements. Technology analysis. Technology solution Vendors Define candidate technology. Technology selection. Technology validation.
- 23. “ SOA is Good…” Pay me now, or pay me later. Make sure you do it right the first time…get the help you need. Don’t be afraid to experiment, and admit you’re wrong…backup and try again. Keep your vendors working with you. Empower those working, so they can work to get things done. Avoid politics, if possible. Learn all you can, but don’t get caught up in the hype. Put standards in their proper place. Small battles win the war…Keep that in mind. Give yourself plenty of time, never skimp on any of the steps.
- 24. Thanks! Blogs: InfoWorld “Real World SOA” Weekly Podcast InfoWorld SOA Report Columns SOA Journal SD Times Web 2.0 Journal eBizq.net Follow me on Twitter (DavidLinthicum)