21 августа 2008 г. 18:07
Ankur, et al.,
Is there an ETA on CTP2? I have a pretty major trading project that goes online for discussions Tuesday (Aug 26). The reliability and features (the notification, availability, etc.) of Velocity will determine if we can leverage .NET in this project at all. Right now, other than DCache, I haven't found any other .NET Cache that can do this. On the flip side, Java's ehCache seems to have been around for a long time and can do everything that we need.
Being a .NET guy, I would prefer to work with .NET. But I need to come up with a .NET solution to the caching requirements before the firm decides to go with Java.
21 августа 2008 г. 20:35Have you checked out ScaleOut StateServer [http://www.scaleoutsoftware.com]? It has excellent support for .NET and is used by several large financial institutions.
22 августа 2008 г. 5:02Модератор
We are planning to release CTP2 in PDC timeframe - end of October. Note that CTP2 is a community preview and as such cannot be rolled out into production. We are also targetting a number of features (embedded and other HPC related features) for our V1+ timeframe that will help with online trading scenarios.
14 октября 2008 г. 9:03Can we have an update on what's new in CTP2?
16 октября 2008 г. 4:59Any hope that we can get an idea on what the licensing will look like when CTP2 is out? I'm sure many of us would like to consider this as a serious contender to ScaleOut, NCache and Coherence, but let's be honest... without any idea of what to expect with the licensing it's a shot in the dark.
28 октября 2008 г. 0:15
Please check out NCache (http://www.alachisoft.com). NCache is the most feature-rich distributed cache for .NET. NCache is also the only 100% native .NET cache in the market. And, NCache also provides ASP.NET Session State storage.
NCache really stands out in its rich set of caching topologies including Mirrored, Replicated, Partitioned, Partitioned-Replica, and Client Cache.
29 октября 2008 г. 15:25
Oracle Coherence now has .Net support so your local/near cache is running within your .Net process. The translation is done over the wire.
Their documentation is a bit sketchy at the moment on the .Net side but it's looking to be viable solution for .Net shops.