Re: [infinispan-dev] Using load balancers for Infinispan in Kubernetes

Hey guys, I'm receiving more and more queries about this solution so I marked [1] for 9.1.0.Beta1 milestone. Please let me know if that's NOT ok [3] :) Thanks, Sebastian [1] https://github.com/infinispan/infinispan/pull/5164 [2] https://github.com/infinispan/infinispan/milestone/78 [3] Just

Re: [infinispan-dev] Using load balancers for Infinispan in Kubernetes

I'm calm!! I'm calm!! [image: pasted1] Being serious now, no offence taken and thanks for clarification Sanne. Next time I'll just publish some percentage difference which will probably express better what I want to tell. And if you see anything wrong with the test methodology that could influence

Re: [infinispan-dev] Using load balancers for Infinispan in Kubernetes

Hey Emmanuel, Comments inlined. Thanks, Sebastian On Wed, May 31, 2017 at 2:56 PM Emmanuel Bernard wrote: > To Sanne’s point, I think HTTP(/2) would be a better longer term path if > we think we can make it as efficient as current HR. But let’s evaluate the > numbers

Re: [infinispan-dev] Using load balancers for Infinispan in Kubernetes

Cool down peoples! http://www.quickmeme.com/meme/35ovcy Sebastian, don't think Sanne was being rude, he's just blunt and we need his bluntness :) Sanne, be nice to Sebastian and get him a beer next time around ;) Peace out! :) -- Galder Zamarreño Infinispan, Red Hat > On 31 May 2017, at

Re: [infinispan-dev] Using load balancers for Infinispan in Kubernetes

Hey Sanne, Comments inlined. Thanks, Sebastian On Tue, May 30, 2017 at 5:58 PM Sanne Grinovero wrote: > Hi Sebastian, > > the "intelligent routing" of Hot Rod being one of - if not the main - > reason to use Hot Rod, I wonder if we shouldn't rather suggest people to >

Re: [infinispan-dev] Using load balancers for Infinispan in Kubernetes

On 05/30/2017 04:46 PM, Sanne Grinovero wrote: > Hi Sebastian, > > the "intelligent routing" of Hot Rod being one of - if not the main - > reason to use Hot Rod, I wonder if we shouldn't rather suggest people > to stick with HTTP (REST) in such architectures. > > Several people have suggested in

Re: [infinispan-dev] Using load balancers for Infinispan in Kubernetes

To Sanne’s point, I think HTTP(/2) would be a better longer term path if we think we can make it as efficient as current HR. But let’s evaluate the numbers of cycles to reach that point. Doing Seb’s approach might be a good first step. Speaking of Sebastian, I have been discussing with Burr,

Re: [infinispan-dev] Using load balancers for Infinispan in Kubernetes

Hi Sebastian, the "intelligent routing" of Hot Rod being one of - if not the main - reason to use Hot Rod, I wonder if we shouldn't rather suggest people to stick with HTTP (REST) in such architectures. Several people have suggested in the past the need to have an HTTP smart load balancer which

[infinispan-dev] Using load balancers for Infinispan in Kubernetes

Hey guys! Over past few weeks I've been working on accessing Infinispan cluster deployed inside Kubernetes from the outside world. The POC diagram looks like the following: [image: pasted1] As a reminder, the easiest (though not the most effective) way to do it is to expose a load balancer