Modern Distributed Messaging and RPC
This document provides an overview of lightweight messaging and remote procedure call (RPC) systems in distributed systems. It discusses messaging systems, typical peer-to-peer and broker-based messaging topologies, characteristics and features of messaging systems, main classes of messaging systems including enterprise service buses (ESBs), JMS implementations, AMQP implementations, and lightweig
Finagleãƒãƒƒã‚«ã‚½ãƒ³ã¸è¡Œã£ã¦ããŸã£ï¼ #finagle_hack - コードジガー
Scalaを始ã‚ã¦æ•°ãƒ¶æœˆã€ã‚ˆã‚Šæ·±ãScalaã‚’å¦ã¶ãŸã‚ã«Twitter製RPCフレームワークã§ã‚ã‚‹Finagleã§éŠã³å€’ãã†ã®ä¼šã¸å‚åŠ ã—ã¦ãã¾ã—ãŸã€‚ ã¾ã£ãŸãã®Finagleåˆå¿ƒè€…ã®ç§ã§ã—ãŸãŒã€æ°´å³¶ã•ã‚“(@kmizu)ã®ã‚ã‹ã‚Šã‚„ã™ã„資料やä¸æ‘ã•ã‚“(@gakuzzzz)ã®è§£èª¬ã®ãŠé™°ã§Finagleã¯è§¦ã£ã¦éŠã¶ã“ã¨ãŒã§ãã¾ã—ãŸï¼ ã‚ã‚ŠãŒã¨ã†ã”ã–ã„ã¾ã—ãŸ(´∀｀) ã¾ãŸã€ä¼šå ´ã‚’æä¾›ã—ã¦ãã ã•ã£ãŸTwitter Japanã®å±±æœ¬è£•ä»‹ã•ã‚“(@yusukey)ã«ã‚‚良ãã—ã¦ã„ãŸã ã„ã¦ã€è‡³ã‚Œã‚Šå°½ãã›ã‚Šã§ã—ãŸï¼ 沢山ã®ãƒŽãƒ™ãƒ«ãƒ†ã‚£ã‚°ãƒƒã‚ºã‚‚é ‚ãã¾ã—ãŸï¼ 以下ã€ãƒãƒƒã‚«ã‚½ãƒ³ã‚’通ã˜ã¦å¦ã‚“ã ã“ã¨ã®ãƒ¡ãƒ¢ã¿ãŸã„ãªã‚‚ã®Ï†(｀д´)ﾒﾓﾒﾓ... Finagle（ãµãƒãーãる）ã¨ã¯ã€Twitter製ã®éžåŒæœŸRPCフレームワークã§ã€RPCã®ã‚·ã‚¹ãƒ†ãƒ を作るãŸã‚ã®ãƒ•ãƒ¬ãƒ¼ãƒ ワーク。 ※ Apache Thriftã®ã‚ˆã†ã«ã€ãれ自体ãŒR
ZeroMQ instead of HTTP, for internal services
Written by August Lilleaas, published July 22, 2013 This article describes how to use ZeroMQ for RPC calls to internal services. HTTP is the canonical choice for public facing services. But for RPC to internal services in systems composed of many small parts, you're probably better off using ZeroMQ instead of HTTP. In summary, the benefits ZeroMQ offers over HTTP are: Multiple concurrent RPC calls
Scala + Finagleã®é…力
1. Scala + Finagle ã®é…力 日本 Scala ユーザーズグループ (ScalaJP) æ ªå¼ä¼šç¤¾ãƒ¦ãƒ“レジ ソフトウェアエンジニア 水島　å®å¤ª
1
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
{{#tags}}- {{label}}
{{/tags}}