What is soa?
Upcoming SlideShare
Loading in...5
×
 

What is soa?

on

  • 534 views

This is a brief taster presentation in to the Service Oriented Architecture which I prepared for my company as part of job handover. I used it sow seeds of SOA and hopefully people took away a sense ...

This is a brief taster presentation in to the Service Oriented Architecture which I prepared for my company as part of job handover. I used it sow seeds of SOA and hopefully people took away a sense of how can we be more SOA like, even if switching completely to SOA would be a step too far. Feel free to use.

Statistics

Views

Total Views
534
Views on SlideShare
534
Embed Views
0

Actions

Likes
0
Downloads
45
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Service-Oriented Architecture SOA is defined by IBM's SOA foundation as follows: "Service-Oriented Architecture (SOA) is an architectural style for creating an enterprise IT architecture that exploits the principles of service-orientation to achieve a tighter relationship between the business and the information systems that support the business." SOA has the following characteristics: It enhances the relationship between enterprise architecture and the business. It allows the building of composite applications as a set of integrated services. It provides flexible business processes. SOA is not simply a technology or a product: it's a style of design, with many aspects (such as architectural, methodological and organisational) unrelated to the actual technology.
  • Business alignment : Services are not based on IT capabilities, but on what the business needs. Services business alignment is supported by service analysis and design techniques. Specifications : Services are self-contained and described in terms of interfaces, operations, semantics, dynamic behaviors, policies, and qualities of service. Reusability : Services reusability is supported by services granularity design decisions. Agreements : Services agreements are between entities, namely services providers and consumers. These agreements are based on services specification and not implementation. Hosting and discoverability : As they go through their life cycle, services are hosted and discoverable, as supported by services metadata, registries and repositories. Aggregation : Loosely-coupled services are aggregated
  • SOA is about behavior, not something you build or buy. You have to change behavior to make it effective. Managing the portfolio of services: planning development of new services and updating current services Some key activities that are often mentioned as being part of SOA governance are: Managing the portfolio of services: planning development of new services and updating current services Managing the service lifecycle: meant to ensure that updates of services do not disturb current service consumers Using policies to restrict behavior: rules can be created that all services need to apply to, to ensure consistency of services Monitoring performance of services: because of service composition, the consequences of service downtime or underperformance can be severe. By monitoring service performance and availability, action can be taken instantly when a problem occurs.
  • Eclipse Swordfish
  • Conhesive pieces of functionality that are atonomas Artifact store – meta information on the services, documentation, EBS – something all services connect to allowing commiication Goverence – to control, monitor and maintance the set of services
  • Plenty of ebooks articles all over the web

What is soa? What is soa? Presentation Transcript

  • What is SOA? Scott Bown
  • This presentation
    • SOA Taster
    • Basic concepts allowing completion of your SOA personal objective
    • Time for discussion
    • Not a in-depth detailed explanation
    • Not how to deploy at this company
  • Summary
    • What is SOA?
    • What is a Service?
    • Key Principles
    • Governance and ESB
    • XML
    • Web services
    • Where next?
  • Service-Oriented Architecture
    • Not a technology or a product
    • There’s no install file
    • Not Java/C/RPG/Groovy etc
    • It’s a style of design:
      • Architecture
      • Methodology
      • Organisation
  • What’s a service?
    • "A service is a discoverable resource that executes a repeatable task, and is described by an externalized service specification.“
    • Business alignment
    • Specifications
    • Reusability
    • Agreements
    • Hosting and discoverability
    • Aggregation
  • Key Principles of SOA
    • Explicit Boundaries
    • Shared Contract and Schema
    • Interoperability
    • Loose coupling
    • Reuse
    • Language/Vendor agnostic
  • Governance
    • Managing the portfolio of services
    • Managing the service lifecycle
    • Using policies to restrict behavior
    • Monitoring performance
  • Enterprise Service Bus (ESB)
  • Artifact Store
    • Like the common libraries database but for services
    • Meta information about the services
      • How to use them
      • What they do
      • Business contacts
  • Technology: XML
    • Open document based standard for standardised information interchange
    • Human readable
    • Example:
    • <dept id=“IT”>
      • <employee id=“123”>
      • <name>Scott</name>
      • </employee>
    • </dept>
  • Technology: WebServices
    • Fit some of the SOA ideals
      • Programming language agnostic
      • Contracts between services
      • Discoverable services
      • Standardised specifications
  • Is using web services using SOA?
    • A: ??
  • Are we currently using SOA principles?
    • A. ??
  • Key things to take away
    • SOA is a way of architecture
    • Services - Cohesive pieces of functionality that are autonomous
    • Artifact store – stores service details so you can reuse
    • EBS – connects everything together
    • Governance – control and monitoring
  • What next?
    • Learn and use XML
    • Learn and use Web services
    • Create services (programs) that are autonomous and loosely coupled
  • Resources
    • www.ibm.com/software/solutions/soa
    • www.eclipse.org /swordfish
    • Google: SOA
    • [Don’t do an image search ‘soa’]
    • IBM DevWorks XML/WS tutorials and free ebooks