[Mono-list] Advantages to Using Mono

Spam Name spamname5 at gmail.com
Tue Jul 26 09:46:50 EDT 2011

That's good to know.  I believe we are going with either postgres of mySQL
with the majority of the data being handled by custom web services we
write.  So sounds like we will be OK from that standpoint.

On Tue, Jul 26, 2011 at 4:59 AM, Matthew Winter <wintermi at teratools.com>wrote:

> Hi,
> On a number of recent projects I have made use of Mono and Linux for
> hosting ASP.NET MVC 3 projects. I found overall the option to work well,
> however there does exist a number of potential pitfalls, mainly around the
> database and ORM solutions. If you are serious about using Mono, then you
> should enforce the use of an open source solution for your ORM and you
> should think very hard about which database you want to make use of. I found
> that many of the "commercial" .NET Drivers either do not work or half work
> under Mono, and generally this is due to the way the driver has been
> written, not the Mono implementation. So when selecting a database, think
> about using MySQL or PostgreSQL, or potentially look at the NoSQL options
> such as MongoDB and Redis. The fact the drivers are open source gives you
> great flexibility when it comes to potentially having to fix the driver when
> used under Mono. Although I have used all 4 of these with great success
> under Mono.
> Regards
> Matthew Winter
> On 26/07/2011, at 5:08 AM, spamname5 wrote:
> > Hey All,
> >
> > I'm trying to make a case for using Mono for a new project coming up and
> was
> > hoping that this list could help me with that decision.  The situation we
> > are in is that we have a smallish development team with extensive
> experience
> > working .net with visual studio 2010.  We would like to develop a new
> high
> > availability web application using jQuery and jQueryUI within a MVC
> > framework while utilizing the development tools in visual studios.  We
> > currently have a web farm consisting of linux servers running apache (and
> > hosting some legacy products that can't get moved) and the shear cost of
> new
> > hardware plus Microsoft license fees for those webservers is forcing us
> to
> > search for another solution.   Here seemingly enters Mono.   Seems that
> mono
> > would be a great fit since we could use mono-tools assist in the
> development
> > in VS2010, as well as using the VS2010 debugging tools and then deploy to
> > our current apache server farm updated to run mod_mono.   There is a bit
> of
> > hesitation however involved with some parties that mono will not provide
> the
> > speed/reliability of a fully native windows solution.  Do people think
> > running mono in this configuration would be reasonable close to running
> > when considering speed and reliability?  In addition if we are using the
> > mono tools migration analysis can we be pretty confident that deployment
> > will be fairly free of compatibility issues?
> >
> > Any thoughts?
> >
> > Thanks for you assistance
> >
> > --
> > View this message in context:
> http://mono.1490590.n4.nabble.com/Advantages-to-Using-Mono-tp3693668p3693668.html
> > Sent from the Mono - General mailing list archive at Nabble.com.
> > _______________________________________________
> > Mono-list maillist  -  Mono-list at lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-list
> _______________________________________________
> Mono-list maillist  -  Mono-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-list/attachments/20110726/9efc3b57/attachment.html 

More information about the Mono-list mailing list