page232
319
While your primary focus is to both provision and entitle your curated data products
to enable consumption by your clients, you must do so in ways that both reduce
consumption friction and keep costs as low as possible. These are some examples:
•
You can insulate your clients from internal delivery failure.
•
Producing client-specific prefiltered data prevents navigation of an
entitlement model for each SQL call.
•
Delivering a data catalog describing relationships and interactions
enables rapid data product integration with client data.
•
Supplying sample SQL statements provides real-world examples to
leverage data products.
All of this reduces the total cost of ownership (TCO), improves system performance,
and removes barriers to adoption for your clients.
Previous chapters focused on technical details supporting application performance
and curation of data products; this chapter focuses on how your clients gain access and
interact with data products along with provisioning an extended suite of tooling. Your
goal is to provision your data products along with contextual information to enable your
clients to rapidly understand, assimilate, and integrate into their environments.
Later in this chapter I will discuss the wider implications of delivering data products
into disparate marketplaces, providing a wider context for your further investigation.
Let’s start with discussing how you entitle your data products.
Entitlement Models
Regardless of the distribution venue for your data products, implementing entitlement
models to ensure a client accesses their licensed data properly incurs both cost and time.
Your approach must work for direct access to the local account where your data
products are curated, for access via an imported Secure Direct Data Share, or for access
via a replicated database.
In this chapter I discuss two entitlement model approaches.
•
Embedded into client-accessible objects
•
Pre-filtered, client-specific data objects
Chapter 9
Client expeCtations