JavaSpaces and caches are too different for a unified API so it's better to provide generic cache support separately, probably via springmodules-cache (which has a somewhat bizarre API but does get the important/difficult things right), see: https://springmodules.dev.java.net/docs/reference/0.7/html/cache.html I have no idea whether a transport is actually the right abstraction for this; a cache on its own is pretty useless, even though send/receive could probably somehow be mangled on top of it. My guess is that a module with regular support classes will provide more value.