[UPDATE: 4 September 2012: This post refers to VFCache at the time of launch and is outdated now that EMC has released VFCache 1.5. You can read my post about that release here.]
Today, EMC announced their much-anticipated server-side Flash product, Project Lightning, under its official name, VFCache.
Lots of folks are writing about VFCache and all the amazing performance-enhancing results it produces. Some are doing deep dives into how it works. Since there are plenty of places to get all that information (there are five VFCache white papers on the EMC company site), I don’t see any reason to cover that same territory in detail here. Instead, after a brief overview of VFCache, I’ll be discussing how it works in a VMware environment.
Full Disclosure: In my position as an EMC employee I’ve had access to VFCache information in advance of today’s launch. I also have access to roadmap information about planned future enhancements and expansions. Under my agreements with EMC, I am not in a position to discuss VFCache futures. I will restrict my commentary to VFCache capabilities “at launch”.
