1 / 35

Services in the Real World

Services in the Real World. dagen@ifi 2007 25. Oktober 2007 Mads Nissen Objectware AS. SpeakerBio – Mads Nissen. Teamleder i Objectware Arkitekt, utvikler, teknologisk kverulant MOSS ( Sharepoint ) SOA .NET & C# Workflow Microsoft Most Valuable Professional ’05/’06

mahala
Télécharger la présentation

Services in the Real World

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Services in the Real World dagen@ifi 2007 25. Oktober 2007 Mads Nissen Objectware AS Services in the Real World, dagen@ifi

  2. SpeakerBio – Mads Nissen • Teamleder i Objectware • Arkitekt, utvikler, teknologisk kverulant • MOSS (Sharepoint) • SOA • .NET & C# • Workflow • Microsoft Most Valuable Professional ’05/’06 • Bachelor Computer Science Services in the Real World, dagen@ifi

  3. Formålet med denne sesjonen.. • Hva er definisjonen av SOA? Er SOA viktig? • Oppdage de grunnleggende arkitekturprinsippene bak enhver vellykket arkitektur, inklusive SOA. • Se påtjenesteri den virkeligeverden • Se på hvordan SOA prinsipper kan få en tjeneste til å yte strålende service (på en smidig måte!) basert på lærdom fra den virkelige verden Services in the Real World, dagen@ifi

  4. Er SOA viktig? Services in the Real World, dagen@ifi

  5. SOA & Service Definitions • Arun Candadai, lead architect, GridScope, Inc. • "SOA is a method of conceptualizing, designing, and building applications by assembling reusable building blocks, each of which is usually represented as a service. At the core, an SOA framework contains a set of services and other infrastructure resources whose interfaces evolve gradually and allow for applications to use them in a manner that is independent of the implementation protocol. To realize true IT and business agility, SOA-driven applications will need to employ an SOA implementation framework consisting of a formal methodology and a set of programmatic interfaces that are dynamic and scalable enough to meet changing and complex business requirements." • This could go on forever.. • Ashok (Ash) Mansukhani • "SOA is a software architecture that enables business agility through the use of loosely coupled services. Services are implementation-independent reusable business functions that are discovered as self-describing interfaces, and invoked using open standard protocols across networks. Services can in turn be combined and orchestrated to produce composite services and business processes, in accordance with pre-defined policies, security and SLAs." • Dave Morris, I.T. Security Lead TransAlta Corp. • "Secure, integrated delivery of IT solutions meeting business requirements. Solutions must implement, optimize and guide business process execution by combining the functionality of separate, discreet, reusable services. SOA moves away from complex application development, promoting a focus on standardizing interfaces between atomic service components with centralized management and distributed implementation." • Sun Microsystems: • An integration architectural style for XML document-based, exchanges using shared, loosely-coupled, network based software services • Open standards-based SOA architectures tend to be best realized using web services as the middleware technology • World Wide Web Consortium (W3C): • Service-Oriented Architecture is:A set of components which can be invoked, and whose interface descriptions can be published and discovered • Kunal Shah • "Interoperability of collection of distributed, loosely coupled heterogeneous services; to orchestrate a series of business tasks, to achieve a specific business process objective." • Thomas Erl, chief architect, XMLTC Consulting Inc. • "SOA is a form of technology architecture that adheres to the principles of service orientation. When realized through the Web services technology platform, SOA establishes the potential to support and promote these principles throughout the business process and automation domains of an enterprise." • Laks • "[SOA] aims at aligning IT services with business processes. It promotes loose coupling between the service providers and service consumers, reuse and incremental integration practice." • Oracle • Service Oriented Architecture is: An Application Architecture that is designed to achieve loose coupling among interacting software applications. SOA provides greater flexibility in developing, integrating, and managing Enterprise Applications • Oracle 2 • Service-Oriented Architecture is:An application architecture in which all functions, or services, are defined using a description language and have invokable interfaces that are called to perform business processes. Each interaction is independent of each and every other interaction and the interconnect protocols of the communicating devices. Because interfaces are platform-independent, a client from any device using any operating system in any language can use the service. • Beat Schwegler • “In short, SOA is about loosely coupled systems, message based communication and business process orchestration.  As an abstract architectural model, it acts as an indirection between the business and the technology model.  Web Services are the preferred implementation technology for loosely coupled and inter-operable systems.”  • Harm Smit • "Many of the SOA definitions given in your article have at least one key notion quoted, such as: • "But none of them has them all. This clearly shows there are many aspects to the SOA concept! Only one of them quotes the notion of autonomy, which IMHO is the most important service attribute in an SOA. To me, this definition (Michael Champion's) is indeed the best amongst those presented in your article. "I definitely disagree with Randy Heffner on the necessity of having a repository cataloging services and their metadata, as well as on the option of using industry standards."

  6. Services in the Real World, dagen@ifi

  7. The road to thecurrentparadigm HISTORY REPEATS ITSELF Services in the Real World, dagen@ifi

  8. From Legos.. Services in the Real World, dagen@ifi

  9. Via duplos.. Services in the Real World, dagen@ifi

  10. …to ”Service Orientation” Services in the Real World, dagen@ifi

  11. Or in a protocolview.. Services in the Real World, dagen@ifi

  12. How far have we gone? • Every level of abstraction allows us to build with larger blocks. • Problem remains the same: Retain evolvability • Dependencies • Versioning • Change and adapt to business requirements But what about:The Eight Fallacies of Distributed Computing Services in the Real World, dagen@ifi

  13. Point in question: It works in the real world! • Every major corporationwas small once: • McDonalds, REMA, IKEA • They’ve all scaled and evolved and beaten thecompetition • Cantheykeeponscaling? • That’spartiallyup to us IT-folks! • Whatarewe missing from the Real World in order to make IT Services work in the same way? Services in the Real World, dagen@ifi

  14. Setter ofexpectations – Real World DescriptionLanguage IRL ServiceS Services in the Real World, dagen@ifi

  15. RWDL: Real-WorldDescriptionLanguage Services in the Real World, dagen@ifi

  16. TheEndpoint Services in the Real World, dagen@ifi

  17. RWDL SetsExpectations Services in the Real World, dagen@ifi

  18. PoorExpectations? Services in the Real World, dagen@ifi

  19. IRL Service Descriptions • Services aredescribedbothexplicitly and implicitly • Services need to be awareoftheirimplicitresponsibility (customerexpectations) and adapt • Customersaretrainedthroughextensive marketing and branding • Great service descriptions and theirrelatedcontractsareoftenadopted by competitors: • McDonalds & Burger King – What’sthedifference? Services in the Real World, dagen@ifi

  20. Breaking the loop – deliveringthe services that ProvidE Great Service! Services in the Real World, dagen@ifi

  21. !Reminder! Services in the Real World, dagen@ifi

  22. The Service Responsibility • REQUIRED: Fulfillthe Service Contract • RECOMMENDED: Fulfilltheexpectationsset to Customers by the Service Description (implicitly or explicitly) • LEADING: SurpasstheCustomersexpectations • The service must handle anythingthat is thrown at him/her Services in the Real World, dagen@ifi

  23. The agile evolution and successof.. THE Customer Service Services in the Real World, dagen@ifi

  24. Service Birth CustomerInfoWeb CustomerService WS-I Basic Profile (Basic WebService) Services in the Real World, dagen@ifi

  25. LightweightConsumers CustomerInfoWeb R&D PHP Playthings CustomerService REST/POX/JSON WS-I Basic Profile (Basic WebService) Services in the Real World, dagen@ifi

  26. CustomerInfoWeb R&D PHP Playthings CustomerReview B2B Exchange CustomerService REST/POX/JSON WS-I Basic Profile (Basic WebService) WS-Security Services in the Real World, dagen@ifi

  27. Service SurpassingExpectations • Suddenlythismashupappearssomewhereontheintranet: • All realestatecustomersofthe bank in the Oslo region plottedon a map. Howdidthishappen? Services in the Real World, dagen@ifi

  28. CustomerInfoWeb R&D PHP Playthings CustomerReview B2B Exchange CustomerService SurpassingExpectations – HOW? REST/POX/JSON WS-I Basic Profile (Basic WebService) WS-Security Architectdecidedthatthe service shouldusecustomeraddress and zipcode to queryMapPoint.NET (or GoogleMapsAPIs) to retrieve latitude and longitude for customers and deliverthis as part ofthecustomerobject. Services in the Real World, dagen@ifi

  29. EvolutionoftheCustomerService • Startedout for oneclientonbasic WS-I tech • Added support for more dialects to attract more consumers (REST etc.) • Got more clients and implemented a smart cachebasedonLucene, supporting more load and more advancedqueries • Responded to clientdemanddelivering sensitive information, but ONLY over a WS-Securityenabledchannel • AddedGeo-positioning (lat/long) informationaboutcustomersproactivelywhichcreatedspontaneousapplications in theorganization Services in the Real World, dagen@ifi

  30. Objectwares approach to Service Orientation and Architecture SOA in Objectware Services in the Real World, dagen@ifi

  31. What is Enterprise Design & Architecture? • ”No non-sense” • Enterprise Architecture • Domain Driven Design • Service Oriented Architecture • Enterprise SOA Patterns • Code (reusable & starting points) • ”How IT fits together” • From EA, to SOA categorized services, realized using documented patterns and deployed on both .NET and Java in real projects. Services in the Real World, dagen@ifi

  32. SOA i Objectware • Vi har utviklet tjeneste-orienterte systemer i lang tid • SOA hypen gikk fra arkitektur til XML og WS-* fokus (definisjon) • Ingen ser ut til å vite hva en tjeneste var.. • Så vi fokuserte på atomet i SOA, nemlig tjenesten.... • ..og det var ikke lett å få på plass.... The Eight Fallacies of Distributed Computing Services in the Real World, dagen@ifi

  33. Services in the Real World, dagen@ifi

  34. Key Takeaways • Services need to mimicthe real world and providegreat service • Just like a normal business, the service evolves to gain ”market share”, and to prosper for more than 20 years • Consumersexpectationsneeds to be met • Services need to evolve in an agile fashion and retainevolvability to keepdoing so • Donewrongwe’llseeyetanother ”Same Old Architecture”. Done right, Services CAN deliver! Services in the Real World, dagen@ifi

  35. Mads – mads@objectware.no Takk for oppmerksomheten! Besøk oss på Objectware stand utenfor! Services in the Real World, dagen@ifi

More Related