Create a set of workflows that implement an Event Driven architecture

[jacky_manai]

My goal is to create a set of workflows that would implement an event-driven architecture pattern.
By implementing patterns: Event Sourcing and CQRS.
All on a kafka and RedisJson + RediSearch infrastructure.

I see for now four workflows to do.
I’ll specify them and then I’ll just have to do them with you

++First workflow (Stage : Backlog) ++: Request/Reply Pattern
1/ Node Webhook (Authentification later)
2/ Node Kafka (publisher with topic Reply + Correlation Id)
3/ Node Kafka Trigger (filtering with Correlation Id)
4/ Node Set for the return

++Second workflow (Stage : Backlog) ++: Business component
1/ Node Kafka Trigger
2/ Node Redis (Json + Search) get the “Bounded context”
3/ Node Function (with node-rules)
4/ Node Kafka

++Third workflow (Stage : Backlog) ++: Read component
1/ Node Webhook (Authentification later)
2/ Node Redis (Json + Search)
3/ Node Set for the return

++Four workflow (Stage : Backlog) ++: Ingestion component
1/ Node Kafka Trigger
2/ Node Redis (Json + Search) get the “Bounded context”
4/ Node Kafka

Tags : #Microservice #EventDriven #EventSourcing #CQRS #BFF (Backend For Frontend)
Stages : Backlog → Roadmap → ToDo → Doing → Release → Deploy

[jan]

Welcome to the community @jacky_manai !

Sorry, I do not understand. What is the question?

[jacky_manai]

Hello,
It’s not a question I consider that in the low code / no code movement we must consider development of workflows in an architectural framework in this case the event-driven approach.

That’s why I would like to share my extensive experience on architecture issues and make the community contribute to a collective project of workflow development in this direction.

Maybe I’m in the wrong place?

Sincerely yours

[Hash]

Thanks for this outline, we’re looking into a similar design using AWS infra, DynamoDb streams, Lambda/SNS etc.