This project is amazing! Thank you so much for sharing it (and also for the monkey island references).
Right now, our fuller embrace of event orientation is stymied by it being difficult to trace the flow of a particular message through various processes. We can't see the workflow forest for the implementation complexity trees.
I would like to use wally to look at the entry points of our GCP PubSub handlers and GraphQL mutation resolvers (gqlgen) and be able to create an HTML document for each of those entry points that documents it's possible side effects, which could be writing to PostreSQL (we use pgx and sqlc), GCS (like S3 but Google), sending PubSub messages, making other GraphQL mutation requests, or writing to GCP Firestore.
This project is amazing! Thank you so much for sharing it (and also for the monkey island references).
Right now, our fuller embrace of event orientation is stymied by it being difficult to trace the flow of a particular message through various processes. We can't see the workflow forest for the implementation complexity trees.
I would like to use wally to look at the entry points of our GCP PubSub handlers and GraphQL mutation resolvers (gqlgen) and be able to create an HTML document for each of those entry points that documents it's possible side effects, which could be writing to PostreSQL (we use pgx and sqlc), GCS (like S3 but Google), sending PubSub messages, making other GraphQL mutation requests, or writing to GCP Firestore.