Cover image for SOA Made Simple [electronic resource].
SOA Made Simple [electronic resource].
ISBN:
9781849684170

9781621989134

9781849684163
Title:
SOA Made Simple [electronic resource].
Author:
Dikmans, Lonneke.
Personal Author:
Publication Information:
Birmingham : Packt Pub., 2012.
Physical Description:
1 online resource (536 pages)
General Note:
Why classify your services?
Contents:
Table of Contents; SOA Made Simple; SOA Made Simple; Credits; About the Authors; About the Reviewers; www.PacktPub.com; Support files, eBooks, discount offers and more; Why Subscribe?; Free Access for Packt account holders; Instant Updates on New Packt Books; Preface; What this book covers; What you need for this book; Who this book is for; Conventions; Reader feedback; Customer support; Downloading the example code; Errata; Piracy; Questions; 1. Understanding the Problem; The importance of information; Example -- insurance company; Mismatch between business and IT.

Duplication of functionality and dataExample -- insurance company; Process silos; Example -- utility companies; Example -- international software company; Example -- insurance company; Strategies to stay ahead; Example -- a software company; Architecture as a tool; Layering of architecture; Models; Requirements; Architecture ontology; Enterprise architecture; Reference architecture; Solution architecture; Project architecture; Software architecture; Service Oriented Architecture; Summary; 2. The Solution; What is a service?; Elements of a service -- contract, interface, and implementation.

Example -- let's have breakfastContract; Interface; Implementation; Example -- ordering a passport; Consumer and provider; Dealing with lots of service providers -- service registry; How can you make sure that people use a service?; From sunny-side-up eggs to IT; Example -- international software company revisited; Contract; Interface; Implementation; Consumer and provider; Reuse; Drivers for services; Common myths; Every service has to be automated by software; Every service is a web service; Consumers of services are always IT systems; Putting it together -- what is SOA?; Solutions.

Example -- utility companyInternational software company -- changing existing processes; Functional duplication -- rationalizing application landscapes; Standardization -- enabling change; Summary; 3. Service Identification and Design; Service identification; Top-down; Example of top-down service identification; Business service identification; Information service identification; Technical service identification; Bottom-up; Meet in the middle; I have identified my services, now what?; Service design; Provide value; Meaningful; Implementation hiding; Trust; Idempotent; Isolated; Interoperable.

IsolationExample: print service; Trust; Security; Fault-prevention and handling; Business faults; Faulty user input; Technical and software faults; Idempotency; Idempotency and statefulness; Granularity; How big should my lasagna be?; Classification; Reusability; Example -- reusability; Example -- good or bad service?; Service definition revisited; Summary; 4. Classification of Services; Service classification revisited; Example -- insurance company; Other classifications; Actor type; Channel; Organizational boundaries; Security level; Architectural layer; Combining classifications.
Local Note:
eBooks on EBSCOhost
Format:
Electronic Resources
Electronic Access:
Click here to view
Publication Date:
2012
Publication Information:
Birmingham : Packt Pub., 2012.