Any java buildpack support for session replication leveraging memcache-release ?

[gberche-orange]

Thanks a lot for sharing this great work, and apologies for the slightly off-context discussion here.

We are looking into ways to leverage the memcache-release for supporting java apps that need session persistence (our initial attempts with native redis session manager came to a dead-end )

We're starting considering forking the java buildpack to add a new tomcat framework extension leveraging https://github.com/magro/memcached-session-manager and in particular applying tomcat configuration similar to the redis tomcat support

Not finding any related thread on cf-dev vcap-dev or java-buildpack issues, I wonder whether LDS Church or other contributors had started some related work or could be interested by such work.

Thanks in advance,

Guillaume.

[youngm]

Hi @gberche-orange

Currently we don't have a strong interest in buildpack configured session support. Most all of our java applications are either Spring Boot apps or they utilize a custom legacy deployment artifact that contains its own server.xml file. In either cases the buildpack cannot do much for auto enabling distributed sessions for these apps. We expect developers to configure it themselves for their projects.

That said I was not aware of https://github.com/magro/memcached-session-manager. I'll begin socializing this component among the teams who are looking for a session solution that they can configure in their server.xml.

Otherwise I fully support you developing such a feature and would be happy to help with any issues you run into with the memcache-release.

[gberche-orange]

thanks @youngm !

That'd be great to find a way to programmatically configure memcached-session-manager into tomcat from a springboot app embedding tomcat. We had previously missed http://stackoverflow.com/questions/25788969/memcached-with-spring-boot . We'll try that next to configure memcached-session-manager without buildpack support.

There's otherwise spring-session which looks promising. I haven't seen support for memcached protocol, however the support for hazelcast in https://github.com/spring-projects/spring-session/pull/277 seems promising. Do you think that would be possible/hard to have opt-in param in memcache-release to expose hazelcast (e.g. in a specific service plan) ?

We're planning to do some simple load tests to compare some session persistence scenarios:

• tomcat session persisted by memcached
• spring session backed by redis
• spring session backed by hazelcast
• hazelcast native session replication

We'll update this issue with results if this can be of interest

[youngm]

@gberche-orange It should be possible to expose a hazelcast port but the multi-tenant aspect of this service is all in the memcache protocol side of things. I didn't even look at integrating the auth deeper into hazelcast so I don't know what that would take or if it would be possible.