MessagePack + Spring MVC or JAX-RS(Jersery) on Spring Boot - QiitaDeleted articles cannot be recovered. Draft of this article would be also deleted. Are you sure you want to delete this article?
Finagle, from Twitter
Finagle is an extensible RPC system for the JVM, used to construct high-concurrency servers. Finagle implements uniform client and server APIs for several protocols, and is designed for high performance and concurrency. Most of Finagle’s code is protocol agnostic, simplifying the implementation of new protocols. Finagle is written in Scala, but provides both Scala and Java idiomatic APIs. GitHub p
BERT and BERT-RPC 1.0 Specification
Purpose BERT and BERT-RPC are an attempt to specify a flexible binary serialization and RPC protocol that are compatible with the philosophies of dynamic languages such as Ruby, Python, PERL, JavaScript, Erlang, Lua, etc. BERT aims to be as simple as possible while maintaining support for the advanced data types we have come to know and love. BERT-RPC is designed to work seamlessly within a dynami
éžåŒæœŸãƒ—ãƒãƒˆã‚³ãƒ«ã®ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆ - sdyuki-devel
éžåŒæœŸãƒ—ãƒãƒˆã‚³ãƒ«ã¨ã¯ã€ã‚µãƒ¼ãƒãƒ¼ã‹ã‚‰è¿”ã£ã¦ãã‚‹å¿œç”ãŒã€å¿…ãšã—ã‚‚è¦æ±‚ã—ãŸé †ç•ªé€šã‚Šã«è¿”ã£ã¦ã“ãªã„プãƒãƒˆã‚³ãƒ«ï¼ˆã‚½ãƒ¼ã‚¹ç„¡ã—。オレオレ定義）。 é †ä¸åŒã§è¿”ã£ã¦ãã‚‹å¿œç”ã¨è¦æ±‚を対応ã¥ã‘ã‚‹ã®ã¯ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã®ä»•äº‹ã§ã€å…¸åž‹çš„ã«ã¯è¦æ±‚ã®ä¸ã«ã‚·ãƒ¼ã‚±ãƒ³ã‚¹ç•ªå·ã‚’入れã¦ãŠãã€ã‚µãƒ¼ãƒãƒ¼ã¯è¦æ±‚ã¨åŒã˜ã‚·ãƒ¼ã‚±ãƒ³ã‚¹ç•ªå·ã‚’å¿œç”ã®ä¸ã«ã‚‚å«ã‚る。 例：MessagePack-RPC éžåŒæœŸãƒ—ãƒãƒˆã‚³ãƒ«ã®ç‰¹å¾´ï¼š イベント駆動型ã®ã‚µãƒ¼ãƒãƒ¼ã®å ´åˆã€ã‚µãƒ¼ãƒãƒ¼ã®å®Ÿè£…ãŒç°¡å˜ã«ãªã‚‹ åŒæœŸãƒ—ãƒãƒˆã‚³ãƒ«ã ã¨é †ç•ªã‚’æƒãˆã¦ã‹ã‚‰è¿”ã•ãªã„ã¨ã„ã‘ãªã„。サーãƒãƒ¼ã®å®Ÿè£…ãŒï¼ˆè¦æ±‚１ã¤ã«å¯¾ã—ã¦ã‚¹ãƒ¬ãƒƒãƒ‰ã‚’割り当ã¦ã¦å‡¦ç†ã™ã‚‹ã®ã§ã¯ãªã）ソケット１ã¤ã«å¯¾ã—ã¦ã‚¹ãƒ¬ãƒƒãƒ‰ã‚’割り当ã¦ã¦å‡¦ç†ã™ã‚‹æ–¹å¼ã ã¨ã‚ã¾ã‚Šé–¢ä¿‚ãªãã¦ã€ç‰¹ã«å®Ÿè£…ã¯ç°¡å˜ã«ãªã‚‰ãªã„。 処ç†ãŒé‡ã„è¦æ±‚ã¨è»½ã„è¦æ±‚を続ã‘ã¦é€ã£ã¦ã‚‚ã€é‡ã„è¦æ±‚ã«è©°ã¾ã£ã¦å¾Œã®å¿œç”ãŒè¿”ã£ã¦ã“ãªããªã‚‹ã“ã¨ãŒç„¡ã„ åŒæœŸãƒ—ãƒãƒˆã‚³ãƒ«ã ã¨ã€å¿œç”ã‚’é€ã‚Šè¿”ã™ã«ã¯ãã®å‰ã®
Thrift vs. Protocol Buffers – Digital Digressions by Stuart Sierra
Overall, I think Thrift wins on features and Protocol Buffers win on documentation. Implementation-wise, they’re quite similar. Both use integer tags to identify fields, so you can add and remove fields without breaking existing code. Protocol Buffers support variable-width encoding of integers, which saves a few bytes. (Thrift has an experimental output format with variable-width ints.) The major
1
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
{{#tags}}- {{label}}
{{/tags}}