page233
320
Both entitlement models have their pros and cons. Figure 9-1 shows both
entitlement models side by side.
Figure 9-1.
Entitlement models
We unpack both entitlement models next; note that both models use the same target
objects albeit with curated data sets.
Embedded Entitlement Model
Most entitlement models are “baked in” to the end user’s queried objects. The reason
is simple: it’s an easy way for developers to deliver quickly at acceptable performance
levels. However, over time, performance often degrades as the data sets become larger
or skewed and the entitlement model becomes more complex. Embedded entitlement
models cost more to maintain over time.
Embedded entitlement models are typically in the form of SQL predicates joining
entitlement objects to data product objects. Each SQL invocation (unless results
are cached) results in the re-evaluation of the entitlement model to identify and
return appropriate data. Figure 9-2 illustrates a typical overview of an embedded
entitlement model.
Chapter 9
Client expeCtations