GitHub - ymmt2005/grpc-tutorial: gRPC tutorial for Japanese readersYou signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
gRPC + AWS: Â Some gotchas
gRPC is great and amazing. So is AWS. But putting them together means learning a few new things. gRPC Just Loves HTTP2 Ok, so you read why prefab.cloud switched to gRPC and you're ready to go! Your first learning will be that traditional ELBs won’t work at all for gRPC. Ok, fine fine. We should be able to use the newer and recommended ALBs, right? Actually no. gRPC is an unapologetic HTTP2 native.
gRPC and Load Balancing
index.md Just documenting docs, articles, and discussion related to gRPC and load balancing. https://github.com/grpc/grpc/blob/master/doc/load-balancing.md Seems gRPC prefers thin client-side load balancing where a client gets a list of connected clients and a load balancing policy from a "load balancer" and then performs client-side load balancing based on the information. However, this could be
ECS + Fargate + gRPCを使ã£ãŸãƒžã‚¤ã‚¯ãƒã‚µãƒ¼ãƒ“ã‚¹æ§‹æˆ - Qiita
ãƒãƒƒã‚¯ã‚¨ãƒ³ãƒ‰ã‚µãƒ¼ãƒã¯æ©Ÿèƒ½æ¯Žã«ãƒžã‚¤ã‚¯ãƒã‚µãƒ¼ãƒ“スã¨ã—ã¦åˆ†å‰²ã—ã€ã‚µãƒ¼ãƒé–“通信ã«ã¯ gRPC を使ã£ã¦ãƒ¢ãƒ€ãƒ³ãªæ„Ÿã˜ã«ã—ãŸã„。 最åˆã®ã‚¤ãƒ³ãƒ•ãƒ©æ§‹æƒ³ ã¾ãš Node.js アプリケーションをコンテナベースã«ã—ã¦ã€Code Pipeline + CodeBuild + ECR + ECS + Fargate ã§ç¶™ç¶šçš„デプãƒã‚¤ï¼†ã‚ªãƒ¼ãƒˆã‚¹ã‚±ãƒ¼ãƒ«ã™ã‚‹ä»•çµ„ã¿ã‚’作ã£ãŸã€‚ ã§ã‚‚ãƒãƒƒã‚¯ã‚¨ãƒ³ãƒ‰ã® gRPC ã§ã‚µãƒ¼ãƒé–“通信を行ã†éƒ¨åˆ†ã§ Unavailable, transport is closing ã¨ã„ã†ã‚¨ãƒ©ãƒ¼ã«ãªã£ã¦ã—ã¾ã„ã†ã¾ãã„ã‹ãªã‹ã£ãŸã€‚ ã“ã® ALB を使ã£ã¦ ECS タスクã«å¯¾ã—ã¦è² è·åˆ†æ•£ã•ã›ã‚‹æ§‹æˆã¯ gRPC を使ã‚ãšã« REST API ã§ãªã‚‰ã†ã¾ãã„ã£ãŸã€‚ HTTP/2 ã® gRPC 㯠ALB ã¨ç›¸æ€§ãŒæ‚ªã„ gRPC 㯠HTTP/2 ãŒå¿…é ˆã¨ãªã‚Šã€ALB ã‚‚ HTTP/2 ã«å¯¾å¿œã—ã¦ã„ã‚‹ãŒã€ãã‚Œã¯
gRPC Load Balancing
This post describes various load balancing scenarios seen when deploying gRPC. If you use gRPC with multiple backends, this document is for you. A large scale gRPC deployment typically has a number of identical back-end instances, and a number of clients. Each server has a certain capacity. Load balancing is used for distributing the load from clients optimally across available servers. Why gRPC?g
Kubernetes上ã§gRPCサービスを動ã‹ã™
Kubernetes上ã§gRPCサービスを動ã‹ã™ã“ã¨ãŒå¤šããªã£ã¦ãã¦ã„る．ãŒé©åˆ‡ã«ãƒãƒ¼ãƒ‰ãƒãƒ©ãƒ³ã‚¹ã‚’ã™ã‚‹ï¼Œãƒªã‚¯ã‚¨ã‚¹ãƒˆã‚’è½ã¨ã•ãšã‚µãƒ¼ãƒ“スをデプãƒã‚¤ã™ã‚‹ãŸã‚ã«ã„ãã¤ã‹æ³¨æ„ã™ã‚‹ã“ã¨ãŒã‚ã‚‹ã®ã§ç°¡å˜ã«ã¾ã¨ã‚ã¦ãŠã． 以下ã®2ã¤ã‚’æ„è˜ã™ã‚‹ï¼Ž Kubernetes Serviceã¯L4ã®Load balancer（LB）ã§ã‚ã‚‹ã“㨠gRPCã¯ã‚³ãƒã‚¯ã‚·ãƒ§ãƒ³ã‚’使ã„ã¾ã‚ã™ã“㨠Kubernetesã®Podã¯æ»ã‚“ã り作られãŸã‚Šã‚’ç¹°ã‚Šè¿”ã™ï¼ŽKubernetesã®Podã«ã¯ãã‚Œãžã‚Œå†…部IPãŒã‚¢ã‚µã‚¤ãƒ³ã•ã‚Œã‚‹ãŒï¼Œã“ã®IPã¯PodãŒæ–°ã—ã作æˆã•ã‚Œã‚‹åº¦ã«å¤‰ã‚る．IPãŒå¤‰ã‚ã£ã¦ã‚‚Podã«ã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹ãŸã‚ã«Kubernetesã§ã¯Serviceã‚’ã¤ãる．Serviceã¯Podを抽象化ã—Virtual IP（VIP）をæä¾›ã™ã‚‹ï¼ŽVIPを使ã†ã“ã¨ã§Podã®IPãŒå¤‰ã‚ã£ã¦ã‚‚Podã«ã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹ã“ã¨ãŒã§ãる． VIPã¯Network i
GitHub - fullstorydev/grpcurl: Like cURL, but for gRPC: Command-line tool for interacting with gRPC servers
grpcurl is a command-line tool that lets you interact with gRPC servers. It's basically curl for gRPC servers. The main purpose for this tool is to invoke RPC methods on a gRPC server from the command-line. gRPC servers use a binary encoding on the wire (protocol buffers, or "protobufs" for short). So they are basically impossible to interact with using regular curl (and older versions of curl tha
gRPC-Web: Moving past REST+JSON towards type-safe Web APIs
gRPC-Web: Moving past REST+JSON towards type-safe Web APIs04.26.17 Michal Witkowski is Improbable’s Principal Tech Lead on SpatialOS and Marcus Longmuir is the Tech Lead of Improbable’s Webtools Team. REST+JSON is the de-facto standard way of building interactions between Web Apps and API servers. However, once you get past the initial ease of the prototyping phase, it shows problems with maintain
API design guide  | Cloud API Design Guide  | Google Cloud
Send feedback API design guide Stay organized with collections Save and categorize content based on your preferences. Changelog Introduction This is a general design guide for networked APIs. It has been used inside Google since 2014 and is the guide that Google follows when designing Cloud APIs and other Google APIs. This design guide is shared here to inform outside developers and to make it eas
Ruby on Rails & Vitessã«ã‚ˆã‚‹â€¨DBスケールアウト
ソーシャルゲームã®ã‚ˆã†ãªé«˜è² è·ãŒã‹ã‹ã‚‹Webアプリケーションã«ãŠã„ã¦ã¯ã€ä½•å, 何百å°ã‚‚ã®ã‚µãƒ¼ãƒãƒ¼ã§ã‚¹ã‚±ãƒ¼ãƒ«ã‚¢ã‚¦ãƒˆã™ã‚‹ã®ãŒå½“然ã®æ™‚代ã«ãªã‚Šã¾ã—ãŸã€‚特ã«DBサーãƒãƒ¼ã§ã¯åž‚直分割ã€æ°´å¹³åˆ†å‰²ã«ã‚ˆã‚‹è¤‡æ•°ã®DBã¸ã®è² è·ã®åˆ†æ•£ãŒè¡Œã‚ã‚Œã€ã‚¢ãƒ—リケーションå´ã§ãƒãƒ³ãƒ‰ãƒªãƒ³ã‚°ã™ã¹ãã“ã¨ãŒå¢—ã—ã¦ãã¦ã„ã¾ã™ã€‚ 今回ã¯ã€G…
gRPC
A high performance, open source universal RPC frameworkLearn more Why gRPC?gRPC is a modern open source high performance Remote Procedure Call (RPC) framework that can run in any environment. It can efficiently connect services in and across data centers with pluggable support for load balancing, tracing, health checking and authentication. It is also applicable in last mile of distributed computi
1
ランã‚ング
ランã‚ング
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
GitHub - jnewmano/grpc-json-proxy: gRPC proxy for Postman like tools
GitHub - uber/prototool: Your Swiss Army Knife for Protocol Buffers
{{#tags}}- {{label}}
{{/tags}}