This article by Vijay Narayanan, defines data services as "the encapsulation of operations on key data entities of relevance to the enterprise." He then makes a general case for data services:
Data services abstract the consumer from having to access or update multiple data sources and are critical in helping maintain data integrity when a consumer needs to work with multiple data sources. Additionally, they help build reusable data services that can be leveraged for multiple projects and initiatives. Data services also perform a critical governance function – they help centralize metrics, monitoring, version management, reuse of data types, and enforce data visibility and access rules.
before addressing specific issues of data services.
Several benefits of using data services (source abstraction, aggregation, reuse, and more) are noted and briefly discussed. Scope of data services is defined very narrowly, "actions on data entities-period," along with why this scoping is important.
The article then looks at data services development following a "contract-first" approach and concludes with a discussion of data services consumption patterns.
Read An Introduction to Data Services for more information on this topic.
/filters:no_upscale()/sponsorship/topic/f1e73882-f385-4f4f-89e2-0799e364e183/CockroachRSB-1684221636780.jpg)
/minibooks/architecture-2023/en/smallimage/logo-1685600892155.jpg){kind=logo}
/articles/api-design-review/en/smallimage/API-design-reviews-are-dead-long-live-API-design-reviews-small-1684310900854.jpg)
/articles/architecture-modernization-domain-driven-discovery/en/smallimage/start-your-architecture-modernization-with-domain-driven-discovery-small-1683106490819.jpg)
/articles/agility-architecture/en/smallimage/logo-1682078942739.jpg){kind=logo}
/articles/architecture-trends-2023/en/smallimage/the-infoq-trends-report-1680611416202.jpeg)
/articles/framework-architectural-decisions/en/smallimage/logo-1679060242842.jpg){kind=logo}
/articles/istio-ambient-mesh/en/smallimage/logo-1678364642232.jpg){kind=logo}
/articles/effective-architecture-conversations/en/smallimage/have-effective-conversations-with-business-stakeholders-about-software-architecture-small-1677231728391.jpg)
/articles/creating-decentralized-apps/en/smallimage/LOGO-1676916574942.jpg){kind=logo}
/presentations/data-streams-architecture/en/smallimage/Kai_Waehner-s-1675025271514.jpg)
/articles/architecture-skeptics-guide/en/smallimage/a-skeptics-guide-to-software-architecture-decisions-small-1672223516348.jpg)
/minibooks/2022-infoq-trends-reports/en/smallimage/LOGO-1672051527011.jpg){kind=logo}
/articles/architecture-architecting-role/en/smallimage/logo-1670404086277.jpg){kind=logo}
/articles/azure-functions-quarkus/en/smallimage/azure-functions-on-quarkus-3-1685542580748.jpg)
/presentations/lyft-cd-benefits-challenges/en/smallimage/tom-wanielista-small-1685002834068.jpg)
/presentations/green-software-growth/en/smallimage/Marco-Valtas-small-1685609473905.jpg)
/articles/test-automation-ci-cd/en/smallimage/effective-test-automation-approaches-for-modern-CI-CD-pipelines-small-1685355310638.jpg)
/articles/impact-machine-learning-climate/en/smallimage/minimising-the-impact-of-machine-learning-on-our-climate-small-1685091723283.jpg)
/articles/kafka-clusters-cloudflare/en/smallimage/tales-of-Kafka-at-Cloudflare-small-1684768928637.jpg)
Community comments
Data Services are an SOA anti-pattern
by Sriram Narayan,
Re: Data Services are an SOA anti-pattern
by Vijay Narayanan,
Re: Data Services are an SOA anti-pattern
by Colin Jack,
Entity Services
by Colin Jack,
Don't confuse SOA with unified data tier
by varun sharma,
Data Services are an SOA anti-pattern
by Sriram Narayan,
Your message is awaiting moderation. Thank you for participating in the discussion.
Why? See Bill Poole's excellent explanation.
Re: Data Services are an SOA anti-pattern
by Vijay Narayanan,
Your message is awaiting moderation. Thank you for participating in the discussion.
Sriram
Are data services an anti-pattern? Just like everything else in architecture, the answer is based on the technology, business, and organizational contexts. The number of data sources, the complexity of data entity structure and data access patterns, volume of data exchange, performance, and degree of decoupling needed between consumers and providers all play into choosing the implementation characteristics of data services. If your organization has several silos of data including a mixture of legacy repositories and each data source integration is unique and costs resources to build and test become factors as well. There are specific concerns and techniques when implementing read-only services vs. read-write services. Finally, data services are not always accessed in synchronous request/reply fashion neither are they always accessed from a task or business service.
Entity Services
by Colin Jack,
Your message is awaiting moderation. Thank you for participating in the discussion.
Isn't this just rehashing the entity services idea yet again?
Personally I totally agree with Bill Poole's analysis.
Re: Data Services are an SOA anti-pattern
by Colin Jack,
Your message is awaiting moderation. Thank you for participating in the discussion.
There's a good discussion of this on InfoQ itself actually:
www.infoq.com/news/2007/06/entity-services
Don't confuse SOA with unified data tier
by varun sharma,
Your message is awaiting moderation. Thank you for participating in the discussion.
SOA Data Services are not just services operating on XML. Instead SOA Data Services are enterprise data management end-points that expose highly optimized engines for working on all types of data.
The inherent inefficiencies of XML, associated with large data handling, and the fact that almost all SOA suites are built upon Java containers – it necessitates the use of a highly optimized caching server within the MW tier to Federate IA using SOA. This added setup/maintenance cost of Caching server basically veers us to utilize SOA Data Service alongside Data Federation Tier.
thequintessentialinquisitor.blogspot.com/2012/0...
Your comments??