Bug 869453

Summary:	Memcached vs HotRod info
Product:	[JBoss] JBoss Data Grid 6	Reporter:	gsheldon
Component:	Documentation	Assignee:	gsheldon
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	jdg-bugs, mhusnain
Target Milestone:	---
Target Release:	6.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-20 23:55:18 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description gsheldon 2012-10-24 00:23:27 UTC

Need to include a topic outlining the benefits of migrating from memcached.

Some points from list discussion should be considered for inclusion in docs:

1) it should be a drop-in replacement with better scale, durability and dynamic elasticity.
2) it's not as fast as JDG with HotRod

memcached wiki http://code.google.com/p/memcached/wiki/NewHardware
 - use case of backing the cache with a database.  
 - the network demand of larger cached items.  

When HotRod protocol is used to connect to a distributed cache in client/server, there is no need to specify hostnames and ports of each node in the remote cache. When using Memcached the hostnames and ports do need to be specified. This can have a significant impact for clients intending to add and remove remote cache nodes frequently (eg on IaaS).

Comment 2 gsheldon 2012-11-22 04:28:05 UTC

Topic on SME pad.

Comment 5 Misha H. Ali 2013-03-20 23:55:18 UTC

Now available at https://access.redhat.com/knowledge/docs/JBoss_Data_Grid/