entmystifizieren von soa, esb, eda …. (source: accenture et al.) it complexity & cost it budgets

Download Entmystifizieren von SOA, ESB, EDA …. (Source: Accenture et al.) IT Complexity & Cost IT Budgets

Post on 05-Apr-2015

103 views

Category:

Documents

0 download

Embed Size (px)

TRANSCRIPT

  • Folie 1
  • Entmystifizieren von SOA, ESB, EDA
  • Folie 2
  • (Source: Accenture et al.) IT Complexity & Cost IT Budgets
  • Folie 3
  • The Software Crisis (ca. 2004) $250B/yr in US (average $430K to $2.3M per project) 16% on time and budget but deliver less than planned (avg 42%) 53% overrun (avg 189%) 31% are canceled, losing $140B/yr
  • Folie 4
  • Folie 5
  • SO ist ein architekturelles Paradigma um verteilte Systeme zu realisieren SO ist evolutionr SO ist Mittel zum Zweck SO kann und sollte ein inkrementeller Prozess sein SOA ist eine Technologie SOA ist revolutionr SOA ist das Endziel SOA bearf einer berholung von Technologie und Business Realitt Mythos Der SOA Hype The only way you can use SOA for everything is to rename everything to SOA Roy Schulte, Gartner
  • Folie 6
  • SOA definiert ein Prinzip Wieder- und Mehrfachverwendung von Softwarekomponenten im Sinne von koppelbaren Services Ein Service ist Applikationslogik die Daten verarbeitet verbunden ist mit anderen Services und ber Nachrichten kommuniziert Service
  • Folie 7
  • Dienste kontrollieren und kapseln ihren internen Zustand. Sie knnen unabhngig von anderen versioniert und weiterentwickelt werden. Sie knnen eigenstndig periodische Arbeiten verrichten. Services are autonomous Dienste sind nie binr miteinander verknpft. Dienste kommunizieren nie ber implemen- tierungsspezifischen Datentypen an der Dienstkante Share schema & contract, not class Anforderungen und Beschreibung von Leistungsmerkmalen werden separat von der Dienst- und Datenbeschreibung gehalten und ausgetauscht. Compatibility based on policy Code an der Dienstgrenze ist explizit fr diesen Zweck vorgesehen. Enthlt keine Logik sondern delegiert an Logik. Das berschreiten von Dienstgrenzen ist explizit im Code sichtbar. Boundaries are Explicit Die vier SO Prinzipien (Tenets)
  • Folie 8
  • CentralizedDecentralizedDistributed Topology Independence
  • Folie 9
  • Prozesse und Business Capabilities in der Architektur Process Model Service Definition Capability Model BPEL4WS Flexibilitt Stabilitt
  • Folie 10
  • Folie 11
  • The ESB Architecture.NET Application J2EE Application Web Service Endpoint ESB Client Software Installed on every node Transport and repository ESB Client Software Installed on every node
  • Folie 12
  • Brokered and Unbrokered Communication BizTalk Server
  • Folie 13
  • Common ESB Characteristics
  • Folie 14
  • Typical Integration Requirements
  • Folie 15
  • ChallengersLeaders Niche PlayersVisionaries Completeness of Vision Ability to Execute Source: Gartner Group Integration Leadership April 2005
  • Folie 16
  • Folie 17
  • Gartner on EDA Event-Driven Architecture: The Next Big Thing Roy Schulte, Gartner, Application Integration & Web Services Summit 2004 Event-Based Application Design: A Different Mind- Set Roy Schulte, Gartner, Application Integration & Web Services Summit 2005
  • Folie 18
  • Processing Events Business impact derives from processing the events Event processing is multi-faceted Correlation ProcessingEvents Routing Orchestration Business Rules Transformation
  • Folie 19
  • Architectural Guidance - Design Patterns "Each pattern describes a problem that occurs over and over again in our environment and then describes the core of the solution to that problem in such a way that you can use this solution a million times over without ever doing it the same way twice. - Christopher Alexander TopologiesPoint-to-pointBroker Message bus Publish/Subscribe Integration Patterns Pipes and Filters Gateway
  • Folie 20
  • Receive Pipeline MessageBox Publish/Subscribe Host Business Activity Monitoring Biztalk Server ReceivePipeline Receive Port Receive Adapter Receive Pipeline Host SendPipeline Send Port Send Adapter Orchestration Business Rules Inference Engine
  • Folie 21
  • Web Services Leadership July 2005 Source: Gartner Group
  • Folie 22
  • Folie 23
  • Folie 24
  • CEP in vier Schritten Detecting patterns of events in a context Understanding aggregating and abstracting patterns of events Predicting the Impact modelling causality between past and future Reactive Planning be prepared eventsreactive processes, in place, ready to go (react to prediction events). defense against situations you dont like Take advantage of situations you like
  • Folie 25
  • Global Event Cloud
  • Folie 26
  • Local IT Systems live in Event Clouds Control systems for power grids, dams, nuclear power stations, etc. Chip fabrication lines Automobile assembly lines Automated warehouses RFID tracking systems
  • Folie 27
  • The Software Crisis (ca. 2004) $250B/yr in US (average $430K to $2.3M per project) 16% on time and budget but deliver less than planned (avg 42%) 53% overrun (avg 189%) 31% are canceled, losing $140B/yr
  • Folie 28
  • Sicht von Microsoft zu: SOA ESB EDA EAI DSI Software Factories CEP neu!
  • Folie 29
  • Connected Systems Integrated Tools and Modeling Connected Systems Integrated Management and Governance FederatedData FederatedIdentity PervasiveWorkflow Integrated User Experience ServiceOrientation
  • Folie 30
  • Interop with other platforms ASMX Attribute-BasedProgramming Enterprise Services WS-*ProtocolSupport WSE Message-OrientedProgramming System.Messaging Extensibility Location transparency.NET Remoting Unified Programming Model
  • Folie 31
  • Die Microsoft Plattform deckt den kompletten IT-Stack ab. Mit.NET als Softwareplattform werden alle Technologien miteinander verbunden und ber VisualStudio programmierbar, ein hohes Ma an Integration ist vorhanden.
  • Folie 32
  • The Software Crisis (ca. 2004) $250B/yr in US (average $430K to $2.3M per project) 16% on time and budget but deliver less than planned (avg 42%) 53% overrun (avg 189%) 31% are canceled, losing $140B/yr

Recommended

View more >