-
Notifications
You must be signed in to change notification settings - Fork 15
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
Articles and Recipes Ideas and Suggestions #22
Comments
Idempotence and its implementation patterns |
Scheduled operations, like cron |
Where do side effects go? |
Sync'ing with partners |
Dealing with external APIs |
End of day reconciliation |
Saugas (in Udi parlance). So... given a particular business process that makes decisions across the results of multiple streams, how does a particular component consume/store that data for future purposes when it's ready to take action |
View Data, aggregating streams and persisting them to some (for instance relational) queryable data store |
Reservation pattern implementations would be a cool one I think? With uniqueness, and expiration examples maybe? |
Pub/Sub implementation, from consumer to message store |
No description provided.
The text was updated successfully, but these errors were encountered: