The Dynamic Data Flow Orchestration pattern dynamically generates and self-heals data flow manifests (DAGs) at runtime from a central context repository
Since you asked :) As feedback, when I opened the email I did notice the length. Because of the bullet points - and they are used effectively because it is a list of points to consider - it was an easy read. But maybe highlight at the start what to expect, e.g. an intro that says “here we introduce a pattern that solves problem x. We’ll describe the pattern, then provide a real world example, then etc…” might be a good sign post so readers know what to expect from the start.
I know you so I knew it would be good value, but for new readers this might help :)
The goal is to create a collab repo where everybody can post their own patterns (or federate them from their own repo), so will move the patterns to a better platform eventually.
But right now im working on getting the pattern template to the 80% mark (or as I put it the "I don't hate this" state). Best way for me to do that is creating them with real content and see what is useful, what is waste and what is missing.
Good point on something that explains the format of the template, ill create an article for that, which I can update as we iterate the template itself.
And that article can go into the final repo so people knwo how to create the patterns and/or read them.
This is a great pattern. Nicely described too!
Thanks Andrew, would love any feedback on how I could make the Pattern template better or clearer.
Since you asked :) As feedback, when I opened the email I did notice the length. Because of the bullet points - and they are used effectively because it is a list of points to consider - it was an easy read. But maybe highlight at the start what to expect, e.g. an intro that says “here we introduce a pattern that solves problem x. We’ll describe the pattern, then provide a real world example, then etc…” might be a good sign post so readers know what to expect from the start.
I know you so I knew it would be good value, but for new readers this might help :)
Thanks Andrew.
The goal is to create a collab repo where everybody can post their own patterns (or federate them from their own repo), so will move the patterns to a better platform eventually.
But right now im working on getting the pattern template to the 80% mark (or as I put it the "I don't hate this" state). Best way for me to do that is creating them with real content and see what is useful, what is waste and what is missing.
Good point on something that explains the format of the template, ill create an article for that, which I can update as we iterate the template itself.
And that article can go into the final repo so people knwo how to create the patterns and/or read them.