The conclusions are interesting too:
- Did not hit any Virgo bugs (yet), stable, didn’t experience any crashes
- Problems only come from [application] code
- Virgo 3.x release improved memory consumption comparing to 2.1
- The learning curve is steep
- Design for modularity upfront is important
- Cannot go back to monolithic app
The last bullet really means they wouldn't want to go back to a monolithic app.
Thanks to Jan and CME Group for being so open about their activity.
Thanks to Jan and CME Group for being so open about their activity.
On 4 Apr 2012, at 17:41, Fetyko, Jan wrote:
ReplyDeleteYou're correct, we don't want to go back to monolithic app.
We have seen the light and will not let it slip away.