Oh Ok. Good to know. Thanks for the info. On Friday, 20 January 2017 11:45:47 UTC-4, William Thurston wrote: > > I use gRPC on AWS and it works great. However, I don't believe ALBs > support trailers in the HTTP/2 spec, so that won't work. Something may have > changed since the last time I looked, but don't count on an HTTP/2 ALB > working. I believe it's HTTP/2 to clients of the ELB but HTTP/1.1 to your > backend servers. > > William Thurston > > On Jan 20, 2017, at 7:17 AM, "[email protected] <javascript:>" < > [email protected] <javascript:>> wrote: > > I haven't tried using gRPC on AWS but it is on my TODO list in near > future. > > Just to add Application Load Balancer does seem to support HTTP/2: > https://aws.amazon.com/blogs/aws/new-aws-application-load-balancer/ > https://aws.amazon.com/elasticloadbalancing/classicloadbalancer/faqs/ > > So theoretically some kind of ALB + EC2 (and ECS) setup should work. > AFAIK API Gateway and Elastic Beanstalk are not possibilities currently. > > Hope this helps. > > On Thursday, 19 January 2017 10:18:18 UTC-4, [email protected] wrote: >> >> gRPC "works" in AWS. That is, you can run gRPC services on EC2 nodes and >> have them connect to other nodes, and everything is fine. If you are using >> AWS for easy access to hardware then all is fine. >> >> What doesn't work is ELB (aka CLB), and ALBs. Neither of these support >> HTTP/2 (h2c) in a way that gRPC needs. >> >> ELBs work in TCP mode, but you give up useful health checking and the >> join-shortest-queue behaviour that makes normal HTTP mode ELBs good. It >> also means you may experience problems with how well balanced your cluster >> is since only individual client connections are balanced rather than >> individual requests to the backend. If a single client is generating a lot >> of requests, they will all go to the same backend rather than being >> balanced across your available instances. >> >> This also means that ECS doesn't really work properly since it only >> supports the use of ELB and ALB load balancers. >> >> If your requirements are not too demanding TCP mode ELBs do work, and you >> can definitely ship stuff that way. It's just not ideal and has some fairly >> major problems as your request rates and general system complexity increase. >> >> On Wednesday, January 18, 2017 at 12:59:40 PM UTC, Daniel Rios wrote: >>> >>> Hey all, >>> >>> I'm interested on trying out gRPC on AWS, but I am new to this and >>> couldn't find examples or documentation related. Is it possible, due the >>> HTTP/2 features?, I also wonder how doable this is. >>> >>> Thanks >>> >> -- > You received this message because you are subscribed to the Google Groups " > grpc.io" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To post to this group, send email to [email protected] <javascript:> > . > Visit this group at https://groups.google.com/group/grpc-io. > To view this discussion on the web visit > https://groups.google.com/d/msgid/grpc-io/d2327ec2-9aa6-47b2-b4bf-a210cb165fb8%40googlegroups.com > > <https://groups.google.com/d/msgid/grpc-io/d2327ec2-9aa6-47b2-b4bf-a210cb165fb8%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > >
-- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/a6a084bb-e264-4a3d-b3a7-3ab56e347781%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
