Is it worth calling out the Gateway UI and database elements of the platform and their advantages?

It would be good capture some points about the strengths & weaknesses and good & bad use cases for SDVI Rally.

Hey @sky-uk/group-distribuion-platform team, it would be great if you can add your input on why we made this platform choice for others to learn about.
Conversely, it would be good to share when not to use it.

A good template to capture this input in a comment on this issue might be:

### Platform Strengths
-

### Platform Weaknesses
-

### Example good fit use cases
-

### Example bad use cases - when to avoid
-

For example (not to be used as fact):

Platform Strengths

• Easy access to off-the-shelf integrations with cloud services for transcoding and packaging.
• Provides an opinionated framework for building content processing workflows ("supply chains") including a database for storing metadata around the "assets" being worked on.

Platform Weaknesses

• A single Supply Chain can't be used to model workflows that make calls out to long running asynchronous workflow steps ("presets").
• It is difficult to access runtime logs for executions of custom python presets
• There is no platform provided simulator/mock to be used when testing custom python presets on their own.

Example good fit use cases

• Creating a reusable workflow for processing media/content files that can effectively scale in the cloud.

Example bad use cases - when to avoid

• Creating a reusable software service that doesn't need to orchestrate the processing of any media/content.

Another piece of detail worth capturing would be around how new components can be onboarded onto this platform and the number of external dependencies a team will need to rely on to use this technology. e.g. how self service is the platform