developers have always known how to deliver successful soa n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Developers have always known how to deliver successful SOA! PowerPoint Presentation
Download Presentation
Developers have always known how to deliver successful SOA!

Loading in 2 Seconds...

play fullscreen
1 / 36

Developers have always known how to deliver successful SOA! - PowerPoint PPT Presentation


  • 106 Views
  • Uploaded on

Developers have always known how to deliver successful SOA!. Microsoft Application Platform Conference 11 . April 2007 Mads Nissen & Totto Objectware AS. SpeakerBio. Totto. Mads Nissen. Teamleder i Objectware Arkitekt, utvikler, teknologisk kverulant MOSS ( Sharepoint ) SOA

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Developers have always known how to deliver successful SOA!' - peyton


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
developers have always known how to deliver successful soa

Developers have always known how to deliver successful SOA!

Microsoft ApplicationPlatformConference

11. April 2007

Mads Nissen & Totto

Objectware AS

Developers have always known how to deliver successful SOA!

speakerbio
SpeakerBio

Totto

Mads Nissen

Teamleder i Objectware

Arkitekt, utvikler, teknologisk kverulant

MOSS (Sharepoint)

SOA

.NET & C#

Workflow

Microsoft Most Valuable Professional ’05/’06

Bachelor Computer Science

  • President i javaBin siden 1998
  • Sun Java Champion
  • CommunityLeader, java.net
  • Sjefskonsulent i Objectware
    • Arkitekt, utvikler, mentor
    • J2EE siden 1997, J2SE/J2ME, AOP, Jini/JavaSpaces, UML, RUP, Agile
    • Programmert professionellt i over 25 år
  • Sivilingeniør fra NTH/NTNU
  • ... og mye mye mer... 

The Value of SOA Delivered

purpose of this session
Purpose ofthissession
  • QuicklyreviewTheChallenge (or oneofthem) in thecurrentmaturing SOA mindset – related to SOA Governance
  • Briefly introduceTheCategorizationFramework for Services
  • Review the concepts of SOA related to the real world with The Merchant Story:
      • Service Descriptions and Contracts..
      • ..in relation to theClient and the Service internals..
      • ..related to the real world ofcommerce
      • This is less stuff – more fluff and food for thought
  • Alignpatterns and technology to thereal-world (more stuffagain..)

Developers have always known how to deliver successful SOA!

slide5

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.

The Value of SOA Delivered

soa i objectware
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

The Value of SOA Delivered

the challenge
Somepoints to thechallenge for successful SOA todayTheChallenge

Developers have always known how to deliver successful SOA!

from legos
From Legos..

Developers have always known how to deliver successful SOA!

via duplos
Via duplos..

Developers have always known how to deliver successful SOA!

to service orientation
…to ”Service Orientation”

Developers have always known how to deliver successful SOA!

or in a protocol view
Or in a protocolview..

Developers have always known how to deliver successful SOA!

how far have we gone
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

Developers have always known how to deliver successful SOA!

point in question it works in the real world
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!
  • Weneed to talk abouthowwe talk about services..

Developers have always known how to deliver successful SOA!

the merchant story
Mixingup SOA terms withthe real world to make your head spinThe Merchant Story

Developers have always known how to deliver successful SOA!

aligning soa with the merchant
Aligning SOA with the Merchant

The Merchant is the analogy for a service in a service oriented universe.

Tying in well-known SOA principles and artifacts with the merchants endeavors

Let’stry to findsome service terms in the real world:

Endpoint

Service Description

Request message

Response message

The Contract

Service implementation

Human 2 Application Service (H2A)

Application 2 application service (A2A)

Aggregated Core Service (ACS)

Core Service (CS)

Developers have always known how to deliver successful SOA!

service description
Setter ofexpectationsService Description

Developers have always known how to deliver successful SOA!

rwdl real world description language
RWDL: Real-WorldDescriptionLanguage

Developers have always known how to deliver successful SOA!

the endpoint
TheEndpoint

Developers have always known how to deliver successful SOA!

rwdl sets expectations
RWDL SetsExpectations

Developers have always known how to deliver successful SOA!

poor expectations
PoorExpectations?

Developers have always known how to deliver successful SOA!

service descriptions
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?

Developers have always known how to deliver successful SOA!

the clerk
Aka - whatsitsbehindthe service endpoint and boundryTHE CLERK

Developers have always known how to deliver successful SOA!

the clerk1
TheClerk

Developers have always known how to deliver successful SOA!

the clerks responsibility
TheClerksResponsibility
  • REQUIRED: Fulfillthe Service Contract
  • RECOMMENDED: Fulfilltheexpectationsset to Customers by the Service Description (implicitly or explicitly)
  • LEADING: SurpasstheCustomersexpectations
  • Theclerk must handle anythingthat is thrown at him/her

Developers have always known how to deliver successful SOA!

the clerks interface
TheClerksinterface
  • May interpret manylanguages – or onlyonebadly
  • May acceptonecurrency – or several (checkexchange rate!)
  • May understand therequest – but have nomeansoffulfilling it
  • May attempt to fulfillyourrequest – eventhough it wasn’tunderstoodcompletely

Developers have always known how to deliver successful SOA!

the clerk 2 0 aka the learning service
Ifour service canadapt to varianceonrequestswecan serve more types ofclients

XML, Strings, CSVs, Voice, Morse-code..

And respond in the same way

Ifour service at leastcanrecordwhat it doesn’t understand wecantrain it

Wait for those AI guys at MIT to comealong

Thisinternalizestheresponsabilityof serving clients to the service

Good for cohesion

Good for versioning

Good for coupling

TheClerk 2.0 aka TheLearning Service

Developers have always known how to deliver successful SOA!

more clerk strategies
More ClerkStrategies
  • Clerkscaling!

Developers have always known how to deliver successful SOA!

howto mimic rwdl
Trying to make Endpoints, Service descriptions, Contracts and Clerkswork in softwareHOWTO: Mimic RWDL

Developers have always known how to deliver successful SOA!

changing contracts
ChangingContracts
  • High-levelcontracts (H2A/A2A) require agile evolvability
      • LowCost
      • Rapid deployment (Time-To-Market)
  • Low-levelcontracts (ACS/CS) require stable evolvability
      • Moderate Cost
      • Not break existingclients
      • Controlleddeployment

Developers have always known how to deliver successful SOA!

evolving h2a a2a services
Evolving H2A/A2A services
  • H2A and A2A layersshould be product-centric and thusveryevolvabletowardstheirclients
    • Ex: Sharepoint, BizTalk, Windows WorkflowFoundation, K2.NET
  • H2A and A2A layersdependon ACS and CS services and canevolveontheirinterfaces
  • If all yourhuman interactionpoints (H2A) and processes (A2A)useyour services, wouldyou make a breaking change?
  • Whataboutself service processorchestration?

Developers have always known how to deliver successful SOA!

evolving acs cs services
Evolving ACS/CS services
  • ACS and CS arecode-centric and stable and needsarchitecturalevolvableinterfacestowardsupperlayers
    • Windows CommunicationFoundation
    • EnterpriseLibrary 3.0
    • EvolvingEndpointPattern
  • ACS and CS must be stable uponchangingdatasources to provide a robust repository
    • EnterpriseLibrary 3.0
    • EnterpriseDomainRepositoryPattern

Developers have always known how to deliver successful SOA!

evolving service endpoint pattern
Evolving Service EndpointPattern

Developers have always known how to deliver successful SOA!

enterprise domain repository pattern
EnterpriseDomainRepositoryPattern

Developers have always known how to deliver successful SOA!

key takeaways
KeyTakeaways
  • Make sure SOA won’t be Same Old Architecture
  • Use Service Categorization to placeresponsibility and achievegoodcohesion and coupling for your services
  • Thinkaboutevolvable services that last for 20 years
  • ThinkEvolvability
  • Create services thatprovidegreat service like in RWDL!
      • Implicit and explicitexpectations
      • Evolvingendpointsthatdon’t break existingcustomers (clients)

The Value of SOA Delivered

takk for oppmerksomheten
Totto – totto@objectware.no

Mads – mads@objectware.no

Takk for oppmerksomheten!

Få med dere neste SOA Sesjon:

Software Factories i den virkelige verden

- Inge Stubdal vil stilne kodehungrige sjeler

The Value of SOA Delivered