specification: FinOps Framework specificationVersion: '1.0' schema: https://www.finops.org/framework/ provider: Spring Data providerId: spring-data created: '2026-05-04' # Provenance stamped 2026-08-11: this artifact was written by the API Evangelist # bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35. method: generated modified: '2026-05-05' reconciled: false tags: - Data Access - Database - Java - Spring Framework - FinOps - FOCUS description: Spring Data is open-source self-hosted software with no vendor invoice. FinOps applies only to the cloud infrastructure that hosts the application (compute, memory) and to the underlying database the Spring Data repositories talk to (RDS, MongoDB Atlas, Redis Cloud, etc.). sources: - https://spring.io/projects/spring-data - https://tanzu.vmware.com/spring-runtime notes: No vendor usage meter for Spring Data itself. Real cost lives in the database / datastore invoice that backs the repositories, plus optional Tanzu Spring support. alignedWith: framework: FinOps Foundation Framework frameworkUrl: https://www.finops.org/framework/ dataSpec: FOCUS dataSpecVersion: '1.3' dataSpecUrl: https://focus.finops.org/focus-specification/v1-3/ publisherName: Broadcom (VMware Tanzu) serviceCategory: Developer Tools billingModel: pricingCategory: Open Source billingFrequency: Annual billingCurrency: USD chargeCategories: - Purchase focusColumns: ServiceName: Spring Data ServiceCategory: Developer Tools ProviderName: Spring Data PublisherName: Broadcom InvoiceIssuerName: Broadcom BillingCurrency: USD meters: - name: spring_runtime_subscription unit: month aggregation: sum dimensions: - contract_tier - cores principles: - name: Visibility description: Spring Data exposes Micrometer metrics for repository-level query timing and HikariCP pool saturation; operators ship these to their observability stack to attribute database cost back to specific repositories and endpoints. - name: Allocation description: Allocate the underlying database spend (RDS, MongoDB Atlas, Redis Cloud) to the team that owns each Spring Data repository. Tag the database resources with team and product in the cloud provider's tagging. - name: Optimization description: Cost levers live in the data layer - tune query plans surfaced via JPA/SQL logging, cap PageSize defaults on Spring Data REST collection resources, and use projections to shrink payload size and downstream egress. - name: Accountability description: Application teams own the cost of the queries their Spring Data repositories generate; platform/SRE owns the shared datastore footprint and any Tanzu Spring support contract. maintainers: - name: VMware Tanzu / Broadcom url: https://tanzu.vmware.com/spring-runtime