By wrapping the Output and solving Strategies in a messaging layer, we would create opportunities to run more expensive solving strategies at scale with minimal latency overhead and increased middleware.
Naturally we will need a suitably expressive encapsulation format - something like XML over JMS seems like an obvious wire transport but we will need to discuss abstractions to keep things vendor agnostic?
Do we need to pull in a senior architect to discuss sequencing and aggregation strategies? I imagine the producer/worker roles need to be distributed for enterprise grade robustness.
cvakiitho
commented
9 years ago
By wrapping the Output and solving Strategies in a messaging layer, we would create opportunities to run more expensive solving strategies at scale with minimal latency overhead and increased middleware.
Naturally we will need a suitably expressive encapsulation format - something like XML over JMS seems like an obvious wire transport but we will need to discuss abstractions to keep things vendor agnostic?
Do we need to pull in a senior architect to discuss sequencing and aggregation strategies? I imagine the producer/worker roles need to be distributed for enterprise grade robustness.