Open Library Environment - Service Oriented Architecture Intro - Jan 14 15 2009.V0.3

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    I’m Stephen Anthony Technology Architect, with CISTI – The Canada Institute for Scientific and Technical Information – at the National Research Council here in Ottawa. I’ve been with NRC for 10 years, and an architect with CISTI for the past 5 years. I specialize in enterprise architecture and service oriented architecture.

    1 Favorite

    Open Library Environment - Service Oriented Architecture Intro - Jan 14 15 2009.V0.3 - Presentation Transcript

    1. Service Oriented Architecture Open Library Environment project regional workshop January 14 2009 - Ottawa Presented by Stephen Anthony
    2. What is SOA?
      • Service-oriented architecture ( SOA ) is a software architecture and methodology where functionality is grouped around business processes and are packaged as interoperable services.
      • Software architecture defines components to use and how those components interact with each other.
      • A Business process is the set of activities and related rules that are used to produce a product or service for a client. It includes all the tasks, data, people, process management activities required.
    3. SOA Advantages
      • Flexibility
      • Reduced development and maintenance costs
      • Interoperability
      • Business-alignment
      • http://www.flickr.com/photos/rightoutloud/2421043521/
    4. Loose Coupling
      • Loose-coupling - Services should maintain a relationship that minimizes external dependencies
      • Helps to ensure the reusability and composability of services – but also promotes good design practices – by only focusing on what the service needs (inputs) and what the services provides (output)
      • Each service should do only one thing – and should do that one thing well.
      • Black box: a mechanism with a known function and an unknown method.
      • http://flickr.com/photos/82705724@N00/119490271/
      • http://flickr.com/photos/fdecomite/453104909
      • http://www.flickr.com/photos/festivefrog/2511300928/
    5. SOA Key Principles
      • Reusability – Services are designed with the intention of promoting reuse (otherwise – don’t make it a service!)
      • Loose-coupling - Services maintain a relationship that minimizes external dependencies – they should be black boxes – the internal workings and data are hidden from view.
      • Composability - Collections of services can be coordinated and assembled to form composite services
      • Statelessness – Services should not depend on the state of other components, systems or services.
      • Abstraction – There can be many levels of services. Don’t make services do too little.
      • Autonomy - Can the service stand on it’s own?
    6. What SOA is not
      • Web services
        • SOA is an architectural methodology
        • Web services are a set of technologies.
      • Automatically interoperable
        • but improves the prospect of interoperability
        • particularly if the best practices and standards are followed
      • A holy grail
        • SOA in itself will not resolve all issues and produce a fully interoperable, sustainable, maintainable, reusable system.
        • but it helps.
    7. SOA Tips
      • Use Noun/Verb syntax when describing services.
        • “ Pay Vendor”, “Find Document”, “Authorize Client”
        • Do something to something.
      • Loose coupling/Black Box.
        • Black box: a mechanism with a known function and an unknown method. .
        • That means no giant “everything” databases
        • Everything done through the service – even database calls – hence “service oriented”.
    8.  
    9.  
    10. SOA Tips
      • Be mindful not to copy bad legacy design.
        • Just making a bad system into a set of services will not improve things... And it’s very likely to make things worse.
      • Use abstraction
        • Thinking about lower-level or higher-level services is often helpful when stuck.
      • Don’t get too detailed too early.
        • Start at the highest level of abstraction and work down.
      • Use as little documentation as possible
        • A few circles, boxes and lines with arrows can do wonders.
        • Saves time when you have to rework it all – and you will.
    11. “ Integrated” Library
    12. SOA as Legos™ Store Metadata Produce Reports Acquire Material Manage Serials Identify Patrons Catalogue Materials Discover Documents Manage Circulation Staff Module
    13. Store Metadata Produce Reports Acquire Material Manage Serials Identify Patrons Catalogue Materials Discover Documents Manage Circulation Staff Module
    14. Store Metadata Produce Reports Acquire Material Manage Serials Identify Patrons Catalogue Materials Discover Documents Manage Circulation Staff Module
    15. Sing
    16.  
    17.  
    18.  
    19.  
    20. Links and References
      • My Blog: http://ea.typepad.com/
      • Anthony, Stephen K. "Implementing Service Oriented Architecture at the Canada Institute for Scientific and Technical Information." The Serials Librarian, 55(01-02), pp. 235 - 253. DOI: 10.1080/03615260801970907
      • Science Library Pad: http://scilib.typepad.com
      • IT Architecture Toolkit by Jane Carbone
      • Service Oriented Architecture For Dummies by Judith Hurwitz , et al.
      • Wikipedia has a decent SOA overview listing lots of good principles in more detail.
    21.  

    + Stephen AnthonyStephen Anthony, 10 months ago

    custom

    1357 views, 1 favs, 1 embeds more stats

    A talk I gave on Jan 14, 2009 at Library and Archiv more

    More info about this document

    CC Attribution License

    Go to text version

    • Total Views 1357
      • 1329 on SlideShare
      • 28 from embeds
    • Comments 0
    • Favorites 1
    • Downloads 50
    Most viewed embeds
    • 28 views on http://ea.typepad.com

    more

    All embeds
    • 28 views on http://ea.typepad.com

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories