Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Ruby & Friends - Taking Go as an example
Search
Richard Lee
April 26, 2014
Technology
3
510
Ruby & Friends - Taking Go as an example
Presented at RubyConf TW 2014
Richard Lee
April 26, 2014
Tweet
Share
More Decks by Richard Lee
See All by Richard Lee
LIFF SDK 的開發者體驗與實用秘訣
dlackty
0
76
Account Kit after 1 year
dlackty
0
56
【Modern Web 2015】愛料理如何打造產品及技術團隊
dlackty
0
33
Chef & Immutable Infrasturcture
dlackty
7
390
軟體上線之後的營運管理
dlackty
8
580
Using CocoaPods for Objective-C Library Management
dlackty
1
310
Does OpsWorks work?
dlackty
10
450
打造愛料理開發及營運團隊
dlackty
79
7.6k
Ruby Toolbox for DevOps
dlackty
22
1.1k
Other Decks in Technology
See All in Technology
Git 研修 Advanced【MIXI 24新卒技術研修】
mixi_engineers
PRO
0
200
テスト・設計研修【MIXI 24新卒技術研修】
mixi_engineers
PRO
0
170
データベース研修 DB基礎【MIXI 24新卒技術研修】
mixi_engineers
PRO
0
210
Azure OpenAI Service Dev Day / LLMでできる!使える!生成AIエージェント
masahiro_nishimi
3
780
さらに高品質・高速化を目指すAI時代のテスト設計支援と、めざす先 / AI Test Lab vol.1
shift_evolve
0
190
データ分析を支える技術 生成AI再入門
ishikawa_satoru
0
380
コミュニティサービスに「あなたへ」フィードを リリースするまでの試行錯誤
takapy
1
150
可視化プラットフォームGrafanaの基本と活用方法の全て
hamadakoji
0
230
DevIO2024_レガシー運用からの脱却 -クラウド活用の実践事例とベストプラクティス-
jun2882
0
210
【基調講演】変える、今ここから ― IoTとAIで紡ぐ未来
soracom
PRO
0
320
ABEMAにおけるLLMを用いたコンテンツベース推薦システム導入と効果検証
cyberagentdevelopers
PRO
1
740
テストケースの自動生成に生成AIの導入を試みた話と生成AIによる今後の期待
shift_evolve
0
180
Featured
See All Featured
Product Roadmaps are Hard
iamctodd
PRO
48
10k
Infographics Made Easy
chrislema
238
18k
5 minutes of I Can Smell Your CMS
philhawksworth
200
19k
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
17
1.5k
Code Reviewing Like a Champion
maltzj
517
39k
Building Better People: How to give real-time feedback that sticks.
wjessup
357
18k
Atom: Resistance is Futile
akmur
261
25k
Save Time (by Creating Custom Rails Generators)
garrettdimon
PRO
13
430
Designing Dashboards & Data Visualisations in Web Apps
destraynor
226
52k
Designing the Hi-DPI Web
ddemaree
276
34k
Music & Morning Musume
bryan
43
5.9k
What’s in a name? Adding method to the madness
productmarketing
PRO
21
2.9k
Transcript
Ruby & Friends Taking Go as an example
... In this talk, I'm going to present several ways
to make such two-way communications between Ruby & Go language.
Richard Lee • CTO @ Polydice, Inc • iCook.tw dev
& ops • Open source lover • @dlackty everywhere
Agenda 1. Why Go language? 2. Go with Ruby using
asynchronous workers 3. Remote Procedure Code 4. Advanced tools
Go Why choose another language when you have Ruby? 1.
Static typing 2. Compiled language 3. Higher level concurrency abstraction (goroutines) 4. No object oriented design
Use cases 1. Command line tools - Heroku's hk 2.
System softwares - Docker 3. DevOps tools - ngrok / packer
Heroku's CLI benchmark ## version $ time heroku version >/dev/null
real 0m1.813s $ time hk version >/dev/null real 0m0.016s ## list $ time heroku apps >/dev/null real 0m3.830s $ time hk apps >/dev/null real 0m0.785s
You don't really understand a language until you use it
in production
Then you might want to use Go in your system
with Ruby
My First Law of Distributed Object Design: Don't distribute your
objects — Martin Fowler
Async processing Use Redis or any message queue based processing.
Resque / Sidekiq friends: • From Ruby to Go • go-workers • goworkers • go-sidekiq • From Go to Ruby • go-resque
go-workers for Resque in action func myFunc(queue string, args ...interface{})
error { fmt.Printf("From %s, %v", queue, args) return } func init() { goworker.Register("MyClass", myFunc) }
...and in Resque class MyClass @queue = :myqueue end Resque.enqueue
MyClass, ['hi', 'there']
Async processing (cont'd) • Pros: • Not fast enough but
quite reliable • easy to scale out • Cons: • Async • Additional setup for queues
Be careful about typing // Expecting (int, string) func myFunc(queue,
args ...interface{}) error { id, ok := args[0].(int) if !ok { return errorInvalidParam } name, ok := args[1].(string) if !ok { return errorInvalidParam } doSomething(id, name) return nil }
Compared to Ruby code class MyClass @queue = :myqueue def
self.perform(i, str) doSomething(i, str) end end
Performance boost • Benchmarked using matrix multiplication a = Matrix[...]
b = Matrix[...] c = a * b puts a * b • 9x faster than Resque • 4x faster than Sidekiq
In some cases, you might need immediate result Then you
need RPC
Remote Procedure Calls Just like function invokation but remotely •
Dynamically-typed • JSON-RPC • MsgPack-RPC • Statically format • Protobuf • Thrift
Dynamically-typed Which means: 1. No need to predefine data format
2. No generated codes for both client & server 3. Quite easy to migrate
JSON-RPC 1. Everybody love JSON! 2. Golang has built-in library
3. Ruby has nice wrappers
JSON-RPC Protocol Can be built on simple TCP connection or
HTTP Request: {"method": "echo", "params": ["Hello JSON-RPC"], "id": 1} Response: {"result": "Hello JSON-RPC", "error": null, "id": 1}
It's demo time.
Client sock = TCPSocket.new "localhost", "5566" call = { method:"RPCMethods.Say",
params:[{"text"=>"Hello, world!"}], id:rand(100) } sock.write JSON.dump call JSON.load sock.readline
Server func (m *RPCMethods) Say(args Args, results *Results) error {
results.Text = args.Text fmt.Println(results.Text) return nil // no error } func (m *RPCMethods) Ping(args Args, results *Results) error { results.Text = "Pong" fmt.Println(results.Text) return nil // no error }
MsgPack 1. MsgPack is efficient binary serialization format 2. Quite
similar to JSON but with binary type 3. Nice packages for most language
MsgPack-RPC 1. MsgPack-RPC is ...RPC using MsgPack 2. Again, nice
packages for different languages
It's demo time.
Client code cli = MessagePack::RPC::Client.new("127.0.0.1", 5566) cli.timeout = 5 v
= cli.call(:echo, "Ruby Conference Taiwan!") cli.close
Statically-typed Which means: 1. Predefine format with special language (IDL)
2. Usually with generated codes 3. Good when you have nice plan
Protobuf 1. Widely used by Google 2. Built in with
Golang 3. However, there's no official RPC mechanism
Thrift 1. Open sourced by Facebook 2. Officially support a
wide range of language 3. Have built in RPC mechanism
Thrift IDL RpcService.thrift namespace go demo.rpc namespace ruby demo.rpc enum
TweetType { TWEET, // 1 RETWEET // 2 } struct Tweet { 1: required i32 userId; 2: required string userName; 3: required string text; 4: optional Location loc; 5: optional TweetType tweetType = TweetType.TWEET }
Thrift in aciton 1. Usually your first start from defining
you service in IDL 2. Generate server / client code using thrift commands 3. Copy that to both side and integrate
But wait, why not just use REST?
RPC v.s. HTTP / RESTful APIs • Persistent connection •
Smaller in size • Easier to implement
Conclusion
Most importantly, learning a new language is always fun and
inspiring
Thank you! Let's Keep in touch Twitter / GitHub: @dlackty