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.

Sign up for GitHub

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

Jump to bottom

[spike] Investigate the use-case for Ballast in server-side applications #52

Closed
cjbrooks12 opened this issue Sep 7, 2023 · 1 comment
Closed

[spike] Investigate the use-case for Ballast in server-side applications #52

cjbrooks12 opened this issue Sep 7, 2023 · 1 comment

Comments

@cjbrooks12
Copy link
Member

With the 4.0.0 updates to InputStrategies, Ballast could conceivably be updated to support distributed processing in a server-side environment. Think of something like the State is held in Redis, and Inputs are AWS SQS messages. It would be interesting to see if it would be possible to build such an integration while maintaining compatibility with the existing Interceptors and API.
@cjbrooks12
Copy link
Member Author

Closing this ticket, as it is superseded by #55 and #56.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cjbrooks12