Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Event-carried state transfer pattern #2434

Open
javatlacati opened this issue Jan 6, 2023 · 2 comments
Open

Event-carried state transfer pattern #2434

javatlacati opened this issue Jan 6, 2023 · 2 comments
Labels
epic: pattern info: help wanted status: stale issues and pull requests that have not had recent interaction type: feature

Comments

@javatlacati
Copy link

javatlacati commented Jan 6, 2023

Event-carried state transfer (ECST) is a software design pattern that allows communication between different components or services in a distributed system by transferring state information along with events. It is often used in event-driven architectures, where events are generated by one component and consumed by another.

In ECST, the state of a system is represented by the data that is carried with an event as it is transmitted from one component to another. When a component generates an event, it includes the current state of the system in the event payload. The consuming component can then use this state information to update its own internal state and process the event. This allows different components to communicate and share state information without the need for explicit requests or responses.

ECST can be a useful pattern for building scalable and resilient distributed systems, as it allows components to operate independently and asynchronously. It can also make it easier to add new components or services to a system, as they can simply consume and process events without needing to be directly connected to other components.

Links:

Acceptance criteria

  • ECST pattern example implemented
@iluwatar iluwatar changed the title event-carried state transfer Event-carried state transfer pattern Jan 6, 2023
@rahul-raj
Copy link
Contributor

@iluwatar
I can work on this.

@stale
Copy link

stale bot commented Apr 19, 2023

This issue has been automatically marked as stale because it has not had recent activity. The issue will be unassigned if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status: stale issues and pull requests that have not had recent interaction label Apr 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic: pattern info: help wanted status: stale issues and pull requests that have not had recent interaction type: feature
Projects
Development

No branches or pull requests

3 participants