Need of SOA database for storing SOA

Download Report

Transcript Need of SOA database for storing SOA

Need for SOA database for storing
SOA data
Divya Gade
Rejitha Rajasekhar
Agenda








Introduction
What is SOA?
SOA Life Cycle
Benefits of SOA
Storage of SOA Data
Mid-Tier Caching Architecture
Conclusion
Discussion
Introduction

Service-oriented architecture (SOA) is a collection
of services which allows applications from different
sources to communicate through standards-based
interfaces. The most common message format used
for implementing the SOA services is XML. So, this
in turn implies that the database designed to store
SOA data must be able to handle XML data with
ease.
SOA Life Cycle
Benefits of SOA






Automation
Increase in agility and productivity
Simplifies management
Stronger connections with customers and
suppliers
Enhanced business decision making
Greater employee productivity
Storage of SOA data - Requirements



Need for federated information management
Need for SOA data caching
Need an unprecedented level of governance
Storing XML data - Databases

Relational databases
–
–
–

File Systems
–

OK if the application is interested only in the data
Not entirely capable of handling SOA data
Inflexibility of relational database schemas
Do not provide advanced querying and management
Native XML databases
–
XML data can be persisted, managed, and treated as XML
Mid-Tier Caching in an SOA



SOA’s need persistence mechanisms to
persist information
This information is frequently requested and
accessed
Cache in the middle-tier
–
Alleviates bottleneck caused by multiple requests
to the same information store
Mid-Tier Caching Architecture




XML database with number of XQuerypowered services
Policy-based Caching Service
Data Repurposing Service
Data Abstraction Service
Policy-based Caching Service




Cache result sets of low performing services
Time to live before the cache is refreshed
Policies based on time of day requests can
determine if the data in the cache is valid for
this request or if the originating source must
be used
If service is not available, results obtained
from the cache
Data Repurposing Service


Provide additional filtering and search criteria
on content returned from a given service
XQuery can be used to repurpose the
content and provide analytics and reporting
on returned content
Data Abstraction Service


Eliminate the need for Web services to be
aware of individual data sources
Eliminates the need to develop separate
clients and web services for each operation
Other Advantages


Since services can run on any system, an
SOA repository can be used to enable the
federation of services
Alleviates performance issues by allocating
the data as close to the data processing as
possible
Conclusion



XQuery is not as powerful as SQL
XML databases still under development and
standards are still being developed
Few more years before SOA databases can
become mainstream for storing SOA data
Discussion and Questions ??
Thank You