-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Remove SMS Provider #7475
Comments
It has been mentioned that this will be implemented with the 4.0 release. We make extensive use of the SMS provider (and fully understand the consequences of doing so) to allow direct grain communication without the need for explicitly calling the destination grain. It allows us to raise an event in the source grain and subscribe to it using implicit subscriptions in the destination grain without the source grain ever needing to know about the destination grain. Event handlers in our grains only ever mutate state in memory and once all grains in the chain have successfully processed events, the state it is committed to storage for all grains in the chain. It is an important part of our infrastructure. I understand the reason for removing it, but could we not keep the feature, but rename it away from the streams namespace? |
I understand that it might not be a very popular decision. Renaming SMS from the stream namespace wouldn't be sufficient, since SMS share some code with persistent streams. This common code is limiting us in enhancing the streaming infrastructure. Ideally, I think SMS users should move to MemoryStreams. Did you considered moving to that? |
For reference - discussed on Discord channel: https://discord.com/channels/333727978460676096/950376855297474611 |
I forgot to update this thread so there is the current plan for 4.0:
The goal is to discourage people completely to use SMS just as another stream implementation, but allow people that want SMS-like behavior to still use it. |
Value: SMS provider lacks decoupling capabilities needed from streams. Our goal is to make sure customers are using in-memory stream provider.
The text was updated successfully, but these errors were encountered: