Brian Loesgen An Early Look At Oslo


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Brian Loesgen An Early Look At Oslo

  1. 1. This Presentation Courtesy of the International SOA Symposium October 7-8, 2008 Amsterdam Arena Founding Sponsors Platinum Sponsors Gold Sponsors Silver Sponsors
  2. 2. An Early Look at Microsoft "Oslo", "Dublin" and related technologies Brian Loesgen Principal Consultant, Neudesic 1
  3. 3. Agenda What is “Oslo”, what are these “related technologies”? Theme #1: Commoditize Interoperability Theme #2: Model-driven Assembly of Applications Theme #3: Software + Services Platform “Dublin”: The Application Server BizTalk Server Roadmap Summary
  4. 4. What is "Oslo"? Defining terms "Oslo" refers to Microsoft’s new modeling platform It's not the code name for a single new product, or new release of a product Whereas Oslo used to refer to all technologies associated with the new wave, it is now being refined as some of those pieces naturally migrate into the products that will be their ship vehicles (ie: .NET 4.0) 3
  5. 5. What is the current state of "Oslo" and related technologies? Microsoft says will tell us more about "Oslo" at PDC in late Oct 2008 No release dates have yet been announced CTP will be available in a PDC timeframe “Dublin” was announced last week The goal today Describe some of the main problems these technologies address Give you a big-picture view of the technology There *will* be changes We are early in the initiative lifecycle Some things are sure to change, e.g., the UIs 4
  6. 6. A whole new wave of technologies… Why is this important? Oslo and related technologies are an ambitious attempt to solve the hard problems associated with designing, creating, maintaining and monitoring distributed, and services-based applications By making everything simpler, this will reduce the skill requirements and reduce code efforts, while also facilitating greater agility to meet changing business requirements 5
  7. 7. What are the core elements? Key innovations Model-driven It’s ALL about models (application models, deployment models, metrics models) The model *IS* the application Models can be run by a variety of hosts Repository-based Models, instances and other artifacts reside in a repository Various tools go through a translation API to create, retrieve, modify and store models 6
  8. 8. Changing The Game: SOA The Three Key Themes 7
  9. 9. Theme #1: Commoditize Interoperability
  10. 10. Simplifying Interoperability Tools, Frameworks, SDKs POX REST Metadata: JSON RSS/ATOM 9
  11. 11. Theme #2: Model-Driven Assembly Of Applications
  12. 12. Conceptual Overview Of Oslo Diagrams SQL Data Access or “Oslo” Language System SQL Data Access Visual DSLs “Oslo” Repository Reposito Models Reposito ries ries Observations Textual DSLs 3rd Party Runtimes 3rd Party Tools 11
  13. 13. End-To-End Integrated Models Tools for modeling the end to end application Models which span and connect the lifecycle Integrated with existing tools suites Ecosystem that provides rich and diverse solutions 12
  14. 14. What’s In The Repository? 13
  15. 15. Business Process 14
  16. 16. Business Process 15
  17. 17. Business Process 16
  18. 18. Extending The Visual Editor Customizing your world What the visual editor displays is determined entirely by the schemas in the repository A schema can have a view experience defined for it Microsoft will ship a set of schemas with pre-defined views Customers and ISVs are free to add their own 17
  19. 19. Using Other Tools Working with the repository Other tools can also be used to work with information in the repository Potential examples: Visio, Visual Studio, System Center tools, tools created by third parties Visio “Oslo” Visual Editor 1) Create business process description 2) Store business 3) Use business process description 18 Repository process description
  20. 20. Working Together Different tools for different roles Business analysts and developers can work together to build WF/WCF applications Repository “Oslo” Visual Editor Visual Studio Workflow definition Workflow as repository definition instance as XAML Business Analyst Developer 19
  21. 21. Developing Composite Applications 20
  22. 22. Theme #3: Software + Services Platform
  23. 23. Conceptual Overview Of Oslo Diagrams SQL Data Access or “Oslo” Language System SQL Data Access Visual DSLs “Oslo” Repository Reposito Models Reposito ries ries Observations Textual DSLs 3rd Party Runtimes 3rd Party Tools 22
  24. 24. Windows Application Server: "Dublin" 23
  25. 25. The problem: Where to host? WF doesn’t mandate a particular host WF/WCF apps can run in nearly any process Writing your own host can be complex MOSS is the only Microsoft-provided WF host 24
  26. 26. Enter “Dublin” A standard WF/WCF Host Runs WF/WCF applications (designed for long-running services) Provides enterprise-grade host services The first Oslo-enabled runtime Additional hosts, including a BizTalk host, will follow 25
  27. 27. Management And Deployment 26
  28. 28. Analytics 27
  29. 29. BizTalk Server A roadmap BizTalk Server 2006 R2 Shipping today BizTalk Server 2009 Scheduled to ship in the first half of 2009 “Synchronizing release” adding support for Windows Server 2008, Visual Studio 2008, and SQL Server 2008 Adds UDDI support, improved B2B, ESB Guidance 2.0, etc. BizTalk Server: The next generation Becomes a host in the “Dublin” application server Microsoft is committed to protecting existing assets, and has announced plans for regular continued future releases of BizTalk Server 28
  30. 30. Planned Releases Breaking the waves Wave 1 Wave 2 Wave 3 Next version of WF Repository “Dublin” (will ship with the Visual editor - BizTalk host .NET Framework “4” - Additional hosts and Visual Studio “10”) “Dublin” - WF/WCF host only 29
  31. 31. Summary Make model-driven applications mainstream Provides more transparent and flexible applications Enables cross domain scenarios: sharing models, keeping data in sync, relationships, querying and policy Network effect: Platform gets more value the more apps use it! Simplify distributed applications Building, deploying, scaling and managing Enhance existing distributed systems platform (e.g., BizTalk, WF, WCF) Apply model-driven approach to distributed systems platform Making more of our application platform model driven over time
  32. 32. Call to action! Go to PDC in Los Angeles