> Is the question of whether or not data access/storage is "in SOA" > fuzzy because there are assumptions about the level of scope of > SOA?
I think so, if you follow a business (or domain, or capability) first approach then you'd end up with larger services that internally manage their own data (and behavior, and message schemas, and data-stores, etc). These large services might choose to access the data through data (or entity) services but obviously they don't have to, and although where/how the data is stored is important it's relegated to being an internal implementation detail of that business meaningful service. However if you follow the whole layered SOA approach, right down to utility/entity services, then the data/entity services become part of your SOA (which has never made any sense to me and used to turn me off SOA).
