PoC Freedom

urn:js:virtue:aspire:proposal:18.1

TL;DR

Allow PoCs freedom to make use of existing Aspire data.

Rational

PoCs can consume any authorised data which is clearly identified as Aspire Production data

PoCs cannot present their data as though it is Aspire Production data, and it is made clear what is Aspire Production data through patterns for each technology (such as Snowflake Presentation Layer Structure Pattern)

PoCs are discouraged from consuming from other PoCs because this can cause dependency problems

Aspire will not invest in facilitating PoC to PoC dependencies, and teams take these on at their own risk. Instead Aspire invests in facilitating the productionisation of PoCs.

Allow PoCs freedom to make use of existing Aspire data, while guiding towards productionisation rather than the potential chaos of PoC to PoC dependencies

Implications

• It is important to be clear what counts as Aspire production data - in Snowflake this can be done using Option 3 of Snowflake Presentation Layer Structure Pattern, where if data comes from the production presentation layer database then it is defined as production, and if it doesn’t, then it isn’t.
  • This production presentation layer data base is not allowed to consume from non productionised environments, so PoCs cannot present their data there
  • It is therefore straightfoward to determine if a PoC is consuming production data because it’s from the production presentation layer
  • This doesn’t technically prevent users from making PoC to PoC dependencies in Snowflake, but Aspire architecture doesn’t