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.
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.