Option 2: Split out schema generation.

This is a (preferred?) alternative to https://github.com/aws-amplify/amplify-backend/pull/2167 .

The idea here is to split out schema computations from data construct creation. So that schema computation can become both input to function and data construct.

Elements:

Split schema generation logic.
Add new concept in construct container to register provider/factory method that can provide arbitrary piece of data.

The upside of this solution is that schema is can be bundling time asset without network calls from lambda.

The downside (if this is a downside at all?) is that we're inventing new way of how verticals can communicate and construct container becomes closer to be generic DI container (like syringe) where modules may register arbitrary logic. (which can be abused if contract between verticals established this way is not guarded with proper types/interfaces which become public api of a vertical).

aws-amplify / amplify-backend

Option 2: Split out schema generation. #2169

🦋 Changeset detected