I can’t believe I still haven’t had a chance to write about Velocity, Microsoft’s recently announced in-memory cache. I think this is just further proof that I have an endless backlog of topics about which I should be writing.
In any case, Derrick Harris of Grid Today has done a great job of connecting the dots for us in his excellent article today. Read the whole article, because he offers good insight on how important this announcement really is, but here’s his analysis of how it affects Digipede:
Whatever emerges from Velocity also should be good news to Microsoft’s technology partners — in particular Digipede, which has been delivering distributed computing to .NET apps and now might get the add-on technology it needs to compete with the big boys. Digipede has received no shortage of praise from customers and commentators alike about its relatively inexpensive and very user-friendly solution, but one of the drawbacks has been its limitation in terms of what types of jobs the Digipede Network can handle, namely CPU-intensive jobs benefitting from parallel processing. If Microsoft and Digipede can make Velocity and the Digipede Network function as a unit and keep the price down, Digipede could find itself selling to a whole new, real-time-data-loving audience. That this integration will occur is pure speculation on my part, but it seems to make sense on the surface.
I have no comment on specifics at the moment, but let’s just say — Derrick, you nailed it.