Project "Velocity" CTP1 Features

re: Project "Velocity" CTP1 Features

omario — Thu, 05 Jun 2008 06:10:28 GMT

Is it something like memcached and Alachisoft's NCache?

re: Project "Velocity" CTP1 Features

omario — Thu, 05 Jun 2008 14:26:05 GMT

Will "Velocity" support System.Transactions?

코드명 Velocity 공개 – 분산 인메모리 캐시

bkchung's WebLog — Fri, 06 Jun 2008 12:01:29 GMT

Microsoft Project Codename "Velocity" : Introducing Project Codename "Velocity" (소식)

re: Project "Velocity" CTP1 Features

pward@testsys.com — Sat, 07 Jun 2008 00:37:26 GMT

We would be using the memory cache instead of going directly to the database, sort of in a lazy write mechanism. We are in an environment where a user hits our database for the same state data ever 30 seconds or so, and updates that data. So, to implement this, we would want to have the web application reading and writing from the memory cache. We would like a queue mechanism to know what is dirty and still on the memory cache. We would then have a service that reads from this queue the dirty objects, and writes them out to the database. It is possible that this service is the notification mechanism you mentioned.

re: Project "Velocity" CTP1 Features

velocityteam — Sat, 07 Jun 2008 09:26:32 GMT

>> We would like a queue mechanism to know what is dirty and

>> still on the memory cache. We would then have a service that

>> reads from this queue the dirty objects, and writes them out to

>> the database. It is possible that this service is the notification

>> mechanism you mentioned.

Notifications seem like a reasonable mechanism to achieve this. We will also consider - in the future - a mechanism to identify the set of changes since a point in time

Thanks

S Muralidhar (MSFT)

re: Project "Velocity" CTP1 Features

velocityteam — Sat, 07 Jun 2008 09:28:14 GMT

>> Will "Velocity" support System.Transactions?

As of this CTP, it doesn't. Currently each operation (Get/Put/Delete) is considered an atomic operation. When we start dealing with multi-object operations, we will consider the use of System.Transaction

Thanks

S Muralidhar (MSFT)

re: Project "Velocity" CTP1 Features

velocityteam — Sat, 07 Jun 2008 09:29:44 GMT

>> Is it something like memcached and Alachisoft's NCache?

There is certainly a set of similar functionality, especially with regards to the core.

Thanks

S Muralidhar (MSFT)

Velocidad de datos

{ WillyXoft .NET } — Sun, 08 Jun 2008 01:30:25 GMT

El equipo de Datos de Microsoft se encuentra trabajando en un proyecto de caching llamado "Velocity"...

re: Project "Velocity" CTP1 Features

phrosty — Mon, 09 Jun 2008 23:08:53 GMT

I would like to see full async support for C++, with i/o completion ports.

re: Project "Velocity" CTP1 Features

sugupta00 — Tue, 10 Jun 2008 09:11:23 GMT

Few things that i think would be important developments..

1) Ability to Write multiple objects in one go instead of writing in a loop.

2) Extending the search methods that can be used like providing support for SQL query to search objects..something similar to LINQ for Collections

3) May be extending support for persistence...providing some kind of interface which can be implemented by user to provide OR mapping.

Цветик-семицветик ... Velocity... или зачем нам еще один Distributed Cache?

Владимир Лещинский — Wed, 16 Jul 2008 16:12:19 GMT

Лети, лети, лепесток, Через запад на восток, Через север, через юг, Возвращайся, сделав круг. Лишь коснешься

re: Project "Velocity" CTP1 Features

john.z — Wed, 17 Sep 2008 07:01:46 GMT

Will velocity provide a output cache provider?

re: Project "Velocity" CTP1 Features

DarthZar — Sat, 18 Oct 2008 03:23:14 GMT

Will 64-bit support be coming? That's a dealbreaker in my opinion, to no be able to address more than 2 GB of ram in an instance. 64-bit support would make this world-class, on par with many of the the commercial products costing tens of thousands of $$.

Thanks for the great work!