liveBook · Manning

Data service

As explained in Microservices Patterns, Second Edition

A service whose primary responsibility is providing other application services with access to data.

A data service primarily gives other application services access to data. In FTGO, the Order Service was split from the Order Data Service. This split could make ordinary changes costly: adding an attribute needed by business logic required changing both services. section 2.2.4

The split also creates design-time coupling. If a change breaks the data service’s REST API, rollout may require adding new endpoint versions, updating clients, and removing unused endpoints. That is substantial work for a change that might otherwise be simple. section 2.2.4

How Microservices Patterns, Second Edition covers it

How deep it goes
Explains cross-service change costs and REST endpoint rollout steps, but does not detail implementation.
Examples
Uses the Order Service and Order Data Service, including an attribute change and breaking API rollout.
What you can do after
Diagnose design-time coupling and plan endpoint version rollouts for breaking data-service API changes.
How it connects
Connects data services with microservices, REST APIs, and design-time coupling.

Also explained in

Compare how 2 books explain data service →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.