Business Ecology Initiative & Service-Oriented Solution

Michael Poulin

Who owns data that the service uses? (part 1)

user-pic
Vote 0 Votes

At a glance, the question in the post title is odd - of cause, it is the service. At the second thought... this answer seems incorrect.

Imagine an organisation that has its own IT. In many cases, the IT, with its computers, sits aside from the business somewhere in the cheap location and on the rented properties. Cloud Computing offers outsourcing (renting) the computers and SaaS talks about renting even the IT's applications. Does the business own the IT in such situations?

The same is with business services in service-oriented world. The fundamental statements are:

• business service owns business meta-data model of data it uses
• business service does not concern where data comes from until the data fits into the service's business meta-data model
• business service does not own data it uses
• business service does not own access to data stores/feeds
• business service does not own the data stores/feeds
• business service uses specialised data services to obtain data
• business service does not manage data it uses as well as data stores
• data that business service uses is owned by the data stores/feeds
• organisation has to construct and maintain shared business data model (centralised or distributed)
• each business service can have its own view on the shared business data model ( like a shared sub-model) and free to interpret data according to the business rules the service implements


I expect that many ask - what confirms such statements? Here are my arguments.

I believe that the power of service orientation is in ability to support business efficiency via flexibility in adopting business changes. One of the most effective adoption techniques is composability offered by services. Majority of business changes may be addressed via new business service compositions. That is, service-oriented (SO) solution is a hierarchy of services and service compositions. At the bottom of this hierarchy, there are self-contained autonomous business services.

The autonomous business services have to demonstrate exceptional flexibility in adopting changes internally and addressing them externally by participating in service compositions. If such service owns data stored in the shared data stores operating under foreign or independent ownership, you can say 'good buy' to the service flexibility.

The opinion that the service has to manage the data it uses and even own the data sources where the used data are stored is very popular. However, the ownership of resources is typical application-oriented approach: applications try to occupy and own all possible entities they depend on at run-time. Service-oriented approach is based on separation of concerns and responsibilities placed on the top of service competition on the QoS arena. This is why I say that the business service does not care where data comes from and how it is stored whilst offered data can fit into business data meta-model owned by the service.

(continued)

No TrackBacks

TrackBack URL: http://www.ebizq.net/MT4/mt-tb.cgi/15539

Leave a comment

Business and Technology ideas, concepts, methodologies and solutions leading to Service-Oriented Enterprise - the primary instrument for obtaining business objectives in fast changing environment

Michael Poulin

Michael Poulin is an enterprise-level solution architect working in the financial industry in the UK and USA.

He specializes in bridging between Business needs and Technology capabilities with orientation on business and technical efficiency, scalability, robustness and manageability. He writes about service orientation, application security and use of modern technologies for solving business problems. Michael contributes to OASIS SOA standards as an Independent Member; he is listed in International WHO's WHO of Information Technology (Historical Society) for 2001. View more

Subscribe

 Subscribe in a reader

Recently Commented On

Categories

Tag Cloud

'Navigating the SOA Standards Landscape, abstraction, active service, ADM, adopt changes, aggregate service, AIA, analysis, API, application, Application Integration Architecture, Architect, architect, architectural mission, architecture, Architecture, architercture, B-SOA, BAWG, BEI, Best Practice, bottom-up, BPEL, BPM, Busienss, busienss case, Business, business, Business Architect, Business architecture, business architecture, Business Architecture, Business Architecture Working Group, business concerns, business data, Business Ecology, business efficiency, business model, business operational model, business organisation, Business Platform Division, business process, Business Process Designer, Business Requirements, business risk, business service, Business service, Business SOA, business value, business view, business-centric, Business-IT problem, capability, CBDI, CBM, choreography, Cloud, Cloud Computing, COBA, collaboration, Collaboration, collaboreation, commodity, component, composition, concept, Conciliator, consumer, COSMIC, cost, cost estimate, cost of ounership, cost of ownership, crisis, CRUD, culture, Cutter Consortium, data ownership, data service, data store, DDD, decision logic, decomposition, demand, design, Design Pattern, development, domain, Domain, Domain Aggregate, Domain Events, Domain Service-Oriented Modelling, DOSOM, DOSOSM, driver, Dynamic Process Edition, EA, EDA, efficiency, end-to-end, Enterprise, Enterprise Architect, Enterprise Architectural Framework, enterprise architecture, Enterprise Architecture, ERP, ESB, event, Event, execution context, Execution Context, expertise, failure, feature, Flexibilit, flexibility, FPA, FSM, Full Functional Points, Functional Points, functionality model, future, Gartner, Governance, governance, granularity, harmonization, Healthcare, IBM, identiy credential, IEEE 1471, IFPUG, implementation, intangible value, Integration-Oriented Architecture, intent, interface, interface orientation, IOA, IT, IT Architect, IT Operation Support, IT organisation, IT without the IT Department, ITIL, Ladder to SOE, leasable Cloud, lease, Loose coupling, Lost in Translation, Management, Manifesto, market, MDA, Michrosoft, Mike Rosen, model, Model-Driven Approach, modelling, Navigating the SOA Standards Landscape Around Architecture, navigation, OASIS, OASIS SOA RA, OASIS SOA RAF, OASIS SOA Reference Architecture Foundation, OASIS SOA RM, ODBC, OMG, ONA, OO, Open Group, Oracle, orchestration, organizational change, participant, pattern, policy, principle, principle of separation of concerns, principles, priority, Private Cloud, Process, process, process-oriented, process-orineted, process-service, project, Provisioning, Pub/Sub, Public Cloud Busienss Requirements, QCon, RA, Real World Effect, Real World SOA, Referemce Architecture, Reference Architecture, Reference Architecture Foundation for SOA, Reference Model, Registry, rent, rentable Cloud, Repository, reuse, RIA, risk, RM, ROI, RPC, rules engine, RWE, SCA, scalability, security, service, Service, Service Autonomy, Service Composability, Service Contract, service contract, service description, Service Description, Service Discoverability, Service Execution Context, Service Orientation, service orientation, Service Oriented Enterprise, Service Relative Autonomy, Service Reusability, Service Separation of Concerns, Service State Management, Service Statelessness, service-oriented, service-oriented eco-system, service-oriented enterprise, Service-Oriented Enterprise, service-oriented environment, ServiceContract, seven properties that differentiate emergent architecture from the traditional approach to EA, situational, sizing, SLA, SO, SO environment, SO Principles, SOA, SOA Manifesto, SOA standard, SOA-RAF, SoaML, SOBA, social networking, SOE, SOEA, solution SOA, SOMA, Spring, standard, study, Summit, supply, T-SOA, tangible value, Technical Architect, Technical Architects, Technical Architecture, technical capabilities, Technology, technology, The Open Group, TOGAF, TOGAF 9.0, top-down, UI, UI Mediator, use, Value Chain, Value Network, Value Networks, view, view model, viewpoint, vision, VPEC-T, Web, Web Service, Web Services, WebSphere, WSDL, ZapFlash,

Monthly Archives

Blogs

ADVERTISEMENT