buy lipitor online
Hurwitz & Associates - Insight is Action

Service Oriented Architecture For Dummies

Service Oriented Architecture For Dummies
Whether you're the IT person responsible for developing SOA or the executive who's trying to get a handle on the concept, this book will help you understand what SOA is, why it's important, and how you can make the most of it.

Learn how to:

  • Identify the main components of SOA and how they work to create business processes
  • Create reusable, flexible systems and avoid common pitfalls
  • Develop a governance strategy for SOA based on your company's philosophy and culture
  • Maximize the benefits of unified communications

Share this book:

Table of Contents

Contents at a Glance

Introduction

Part I: Getting Started with SOA
Chapter 1: Getting to Know SOA
Chapter 2: Are You Ready for SOA? A Self Test
Chapter 3: Making Sure SOA Happens
Chapter 4: SOA Quick Start: Entry Points for Starting the SOA Journey

Part II: Introducing SOA Basics
Chapter 5: Understanding Software Architecture
Chapter 6: Working with Software Components
Chapter 7: Discovering the Main Components of SOA
Chapter 8: Playing Fast and Loose: Loose Coupling and Federation
Chapter 9: The Collaborative Lifecycle of the Business Process

Part III: Nitty-Gritty SOA
Chapter 10: (e)Xplaining XML
Chapter 11: Dealing with Adapters
Chapter 12: Discovering the Service Broker
Chapter 13: The Enterprise Service Bus
Chapter 14: The SOA Service Manager

Part IV: SOA Sustenance
Chapter 15: SOA Governance
Chapter 16: SOA Security
Chapter 17: Turning Data into Services
Chapter 18: SOA Software Development
Chapter 19: The Registry and the Repository
Chapter 20: Putting Quality into SOA

Part V: Real Life with SOA
Chapter 21: Financial Services
Chapter 22: Government
Chapter 23: Healthcare
Chapter 24: Hospitality and Travel
Chapter 25: Information Services
Chapter 26: Manufacturing and Distribution
Chapter 27: Retail
Chapter 28: Telecommunications
Chapter 29: Utilities and Energy

Part VI: The Part of Tens
Chapter 30: Ten Swell SOA Resources
Chapter 31: Ten SOA No-Nos

Read a Chapter

Chapter 1 Getting to Know SOA

In This Chapter

▶ Finding out why you should care about SOA
▶ Liberating business from the constraints (and tyranny) of technology
▶ Illustrating the need for SOA
▶ Saving bundles by using what you have
▶ Expanding your SOA to customers, partners, and suppliers
▶ Focusing on function

Service oriented architecture (SOA) is a hot topic being bandied about by IT vendors across the globe.  IBM, Hewlett-Packard, Software AG, Oracle, SAP, and Microsoft (just to drop a few names) are all singing from the SOA songbook, and hundreds of vendors are adding their tunes as we speak.  "What's SOA?" you ask.

We suspect that you've already skimmed a dozen articles and read (or deleted) hundreds of e-mails from vendors pushing SOA, but the answers you've gotten so far have been, well, vague and inadequate.  The short answer is that SOA is a business approach to building IT systems that allows businesses to:

✓ Leverage existing assets

✓ Create new ones

✓ Easily enable the inevitable changes required to support the business

For you impatient readers out there, we expand on this short answer in Chapter 5. However, right now, we think the more important question is, "Why should I care about SOA?" In this chapter, we try to answer this question.

The promise of service oriented architecture is to liberate business from the constraints of technology, unshackling technologists and business leaders from the chains they themselves have forged. ("IT workers of the world, unite! You have nothing to lose but your chains!" as it were.) This has major implications both for the business and for the IT structure that supports the business.  From our perspective, one of the most important aspects of SOA is that it's a business approach and methodology as much as it is a technological approach and methodology. SOA enables businesses to make business decisions supported by technology instead of making business decisions determined by or constrained by technology. And with SOA, the folks in IT finally get to say "yes" more often than they say "no."  We pronounce SOA to rhyme with boa (bow-uh). Stretching it out by clearly articulating each letter (S-O-A) is perfectly acceptable but might leave you stymied when we say things like, "SOA what?"