Credential caching on distributed java app

[Matthew Macchia]

Howdy,

I've got a distributed java application with lots of adwords accounts with their own ad words sessions. We cache each ad words session locally on the box on startup, however the best practices guide suggests a distributed cache:

https://developers.google.com/adwords/api/docs/guides/authentication

Data store

A central data store can be used to share the credential between processes and servers.

You can make use of an existing data store or deploy one specific to the sharing of credentials between servers. Solutions include caching servers (such as Memcached or Infinispan), or NoSQL data stores (such as MongoDB).

I want to move to this direction since this is an expensive operation. The main problem here is that the objects in the Java AP,I AdWordsSession and Credential are not light weight DTO's and they are not serializable.  I would normally convert them to JSON and store them in redis, but I can't really do that in this situation.

What strategy should we use to move those to a distributed cache?

I've read these two posts which speak more to caching locally then distributed:

https://groups.google.com/forum/#!searchin/adwords-api/cache$20credentials$20java|sort:relevance/adwords-api/zf0slvrjkMs/a951xWKuUP4J

https://groups.google.com/forum/#!searchin/adwords-api/cache$20credentials$20java|sort:relevance/adwords-api/sQYns2rzNJU/JrRUKeqYVu4J

Let me know if I'm being too vague and I'll elaborate.

Thanks

-matt