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

InMemory Stream Issues, would you replace with Kafka or use Orleans Persistent streams #9392

Open
sajjadhs opened this issue Mar 17, 2025 · 0 comments

Comments

@sajjadhs
Copy link

Hi, In Memory streams are not recommended for production use, but I'm using it as I needed to remove any latencies, and my system is tolerant against recovering lost data.
But I see many issues with Orleans stream when running multiple instances, and for the times when some message sizes are big or the number of messages is too high, in such scenarios I get grain locating issues, or missing some hops to silos, or getting issue with an object not found in the cache, etc.

So I decided to fully replace in-memory streams, considering above mentioned issues, would you replace Orleans streams with AWS-hosted or self-managed Kafka, or would go with persistent stream options with Orleans?

For me replacing with some persistent stream options for Orleans looking to be simpler but since it will be out of my ecosystem, in which is all resources are on AWS, going to Microsoft Azure will add extra hops to my works.

@sajjadhs sajjadhs changed the title InMemory Stream Issues, would you go with Kafka or use Orleans Persistent streams InMemory Stream Issues, would you replace with Kafka or use Orleans Persistent streams Mar 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant