"Peter Haider" > Hello Newsgroup, > currently now i am working with Classic ASP. > In most cases i use Mysql or MS SQL 2k. So far so good. > What i want to know, is it worth to evaluate Cache against .Net?
Not really a proper comparison. .NET is an awesome system with many arms and legs. Microsoft has thought it out very well and it has some very cool stuff. But it is not really a product. It is a set of tools and methods that are fairly well integrated to allow developers to crank out product. Cache is a technology that competes with some portions of .NET and utilizes others. It turns out that the database components of .NET are, by, far its weakest elements. That, and you are constrained by the fact that everything has to run on MS software. Those silly ISC ads with the half racehorse, half cow are correct. With .NET tools you have a powerful, OO front end that squanders much of that when talking to a RDBMS. Some possible scenarios: Cache as a data store for a VB.NET or ASP.NET front end. Powerful, more flexible object model, real object storage and still very fast. Far fewer maintence issues than SQL server. Disadvantage: Cache does not (to the best of my knowledge) have native .NET deployment support. I do not fully understand what is involved here but I suspect it is (if I know Microsoft) a pain to develop. Ease of deployment is a huge advantage of .NET. However, most of the deploment hassle is in the UI, so you still benefit from .NET Build an app with CSP and Cache. Awesome performance because there are many fewer moving parts. .NET is out of the picture but the system will run perfectly on Linux, Solaris and Mac boxes! Peter's post has a good summary of object issues and CSP. He is right in saying that converting to ASP.NET is a very big step. A conversion to CSP would be no more difficult. A final note: Novel recently took over the leadership of the MONO project and has released version 1.0. This is an open source framework running under LINUX that brings much of .NET technology to LINUX. This is worth taking a look at. If this technology pans out, I would be interested in seeing some support from ISC. > I think to migrate my application to DotNet, Cache could be also an option. > Do i stay with Dotnet on the right side or is this only a markting > statement? > And what is your experiance to position a product with Cache against DotNet > in the market, could i stand? In a web app, it make now difference since the user only sees web pages. I would go with Cache and CSP/WLD/PHP. If you have to deploy on client machines, a pure .NET solution is very attractive way to go. -- John Bertoglio Senior Consultant co-laboratory office: 503-538-8691 mobile: 503.330.6713 fax: 503.538.8691 www.co-laboratory.com > Hope to hear (read) a lot of your experiance. > Best regards > Peter Haider > >
