April 7, 2006Laterooms.com gives up on MonoPosted 1574 days ago on April 7, 2006Is Mono, the open-source implementation of Microsoft's .NET Framework, ready for production use? Maybe in some scenarios, but the experience of laterooms.com suggests scalability issues. Laterooms is a hotel booking site which claims 32,000 daily visitors. The UK-based company migrated its site from PHP to .NET, with the intention of running on Mono. "Functional testing went well", said Gavin Hamill in a post to Mono's public mailing list, but when the site went live it was "a cataclysmic disaster, both technical and financial...Our public site now runs on Windows, and has been running perfectly." The bug seems to be memory-related. "Memory usage of the mono process slowly spirals upwards until the machine swaps so heavily it becomes unresponsive", says Hamill. The upside of this particular tale is that Laterooms was apparently able to switch its application from Linux to Windows with few if any changes to the code. That's actually a benefit of Mono; and in theory a frustrated Windows .NET developer could move in the other direction. Mono is good for the .NET platform, and is gradually maturing, but not soon enough for Laterooms. Someone asked whether suitable technical help might persuade them to switch back. "We're many miles past that stage," said Hamill. See this posting for more details. I'm interested in other experiences with Mono - emails and comments welcome. Re: Laterooms.com gives up on MonoPosted 1571 days ago by Tim Anderson • • • ReplyTrue, VB support is not Mono's top priority. Re: Laterooms.com gives up on MonoPosted 1556 days ago by Gavin Hamill • • www • Reply
Hi :) (It's amusing to see your article on the first page of google hits for 'laterooms', BTW) |
Recent postsUsers plead with Borland to give up .NETIE7 to be released 18th October,... If Microsoft doesn't use UAC, why... Google's unsettling lack of direction Vista security: now prove it |
Re: Laterooms.com gives up on Mono
Posted 1571 days ago by Devin • • • Reply> in theory a frustrated Windows .NET developer could move in the other direction.
Unless your code happens to be in VB.NET in which case Mono's compiler is so poor it'll never compile.