One technology that continues to push the limits of data caching and massive web persistence is Gear6's Web Caching Server. Think of Gear6 Web Cache as a Memcached distribution on steroids. It can run in the datacenter or the cloud (EC2, GoGrid) while reducing latency and increasing application performance for large Web 2.0 properties. Today, Gear6 announces the completion of a whole new layer of persistence in their Web Cache solution. DZone spoke with Joaquin Ruiz, the VP of Products at Gear6, and Mark Atwood, the Director of Community Development, about the new capabilities in Web Cache. Redis Integration
Gear6's focus was initially on expanding the capabilities of Memcached and its ability to quickly onboard and manage dynamic data. In their research of modern web architectures, Joaquin Ruiz said Gear6 had found many web developers who wanted to persist their mountains of unstructured data in their natural form, instead of force fitting it into an RDBMS. Persistence was especially important with ad-driven sites, said Ruiz. "They were storing hundreds of millions of cookies and they didn't want to instantiate a SQL-driven data structure behind that," said Ruiz Now Gear6 has shifted its focus towards accelerating structured MySQL data sets in their Memcached server and deploying a NoSQL architecture. Today's release of Gear6 Web Cache integrates their Memcached interface with operational query capabilities and a NoSQL backend. Gear6 decided to use the key-value store Redis because it already had traction among NoSQL users. Mark Atwood said that Gear6 chose a key-value store (as opposed to a document-store or graph database) because it is simple work with. "Cassandra and CouchDB are very usable and useful, but they're not as straightforward as a key-value store," said Atwood. Gear6 wanted a technology that developers from many different backgrounds could pick up and work with. Read more: DZone
Gear6's focus was initially on expanding the capabilities of Memcached and its ability to quickly onboard and manage dynamic data. In their research of modern web architectures, Joaquin Ruiz said Gear6 had found many web developers who wanted to persist their mountains of unstructured data in their natural form, instead of force fitting it into an RDBMS. Persistence was especially important with ad-driven sites, said Ruiz. "They were storing hundreds of millions of cookies and they didn't want to instantiate a SQL-driven data structure behind that," said Ruiz Now Gear6 has shifted its focus towards accelerating structured MySQL data sets in their Memcached server and deploying a NoSQL architecture. Today's release of Gear6 Web Cache integrates their Memcached interface with operational query capabilities and a NoSQL backend. Gear6 decided to use the key-value store Redis because it already had traction among NoSQL users. Mark Atwood said that Gear6 chose a key-value store (as opposed to a document-store or graph database) because it is simple work with. "Cassandra and CouchDB are very usable and useful, but they're not as straightforward as a key-value store," said Atwood. Gear6 wanted a technology that developers from many different backgrounds could pick up and work with. Read more: DZone
Posts
0 comments:
Post a Comment