-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Martin,
On 2/19/20 07:22, Martin Grigorov wrote:
> Hi Jonathan,
>
> On Wed, Feb 19, 2020 at 12:55 PM Jonathan Yom-Tov <
> jonathan.yom...@sysaid.com> wrote:
>
>> hi Chris,
>>
>> Do you have a link? I wasn't able to find one on Google, unless
>> you
Hi Jonathan,
On Wed, Feb 19, 2020 at 12:55 PM Jonathan Yom-Tov <
jonathan.yom...@sysaid.com> wrote:
> hi Chris,
>
> Do you have a link? I wasn't able to find one on Google, unless you mean
> https://bitnami.com/stack/tomcat/helm.
>
I think Chris meant the **MembershipProvider classes at
https://
hi Chris,
Do you have a link? I wasn't able to find one on Google, unless you mean
https://bitnami.com/stack/tomcat/helm.
thanks,
Jon.
On Tue, Feb 18, 2020 at 5:44 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Jon,
>
> On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon,
On 2/16/20 10:06, Jonathan Yom-Tov wrote:
> What kind of configuration do people usually use when deploying on
> a public cloud (e.g. AWS)? An auto-scaling cluster with session
> replication? A auto-scaling cluster with all sessions stored in a
We are also using redis based option.
On Sun, 16 Feb 2020 at 17:32, Jonathan S. Fisher wrote:
> We're doing the second: sessions stored in a Redis cluster with
> sticky sessions. This topology is simple and it scales pretty easily until
> it doesn't anymore [couple thousand simultaneous users].
We're doing the second: sessions stored in a Redis cluster with
sticky sessions. This topology is simple and it scales pretty easily until
it doesn't anymore [couple thousand simultaneous users]. You'll need to
judiciously use your debugger and unix tools to find bottlenecks, as
they're often hidde
