page265
352
Figure 9-12.
Sharing limitation
Data shared within the same CSP and same region is readily achieved by enabling
the consuming account to access a single share. Offering multiple account consumption
for an existing share is a great way to win customer loyalty and significantly reduce both
friction and copy costs.
Hydration Approach
Regardless of where you distribute your data products, you must ensure the consistent
application of entitlement across disparate data distribution venues. Your approach
must consider not just Snowflake, but all tooling and products dependent upon data
products mastered within Snowflake.
To protect your clients from internal system failure, you must also consider how,
and from where, you will hydrate your data. This point may not be obvious: your
clients should not be forced to invoke their disaster recovery plan due to an upstream
data supply failure from a provider. Furthermore, you should consider hydrating from
multiple sources wherever possible.
The timeliness of data must also be considered. If you curate your data within a
single environment and propagate change to consumers, with the exception of a Secure
Direct data share, latency is introduced. How you address latency is important; in the
previous chapter you saw how parallelizing feeds can reduce latency.
Chapter 9
Client expeCtations