Downloaded 79 times
Uploaded byIlya Grigorik
0-60 with Goliath: Building High Performance Ruby Web-Services
The document discusses Goliath, an open source Ruby web framework for building high-performance web services. It provides an overview of Goliath's features like asynchronous HTTP processing, routing, middleware, streaming responses and websockets. Examples are given showing how to write simple Goliath applications and APIs. The document also discusses how Goliath enables building asynchronous apps using techniques like EventMachine and Fibers.
More Related Content
Similar to 0-60 with Goliath: Building High Performance Ruby Web-Services
0-60 with Goliath: Building High Performance Ruby Web-Services
- 1. 0-60 with Goliathbuildinghigh-performance (Ruby) web servicesIlya Grigorik@igrigorik
- 2. conn =EM::HttpRequest.new('http://gogaruco.com')r1 =conn.get:path => "speakers.html", :keepalive => true# 250 msr2 =conn.get :path => "schedule.html"# 300 ms# wait until done …Answer:All of the above!Total execution time is:250 ms300 ms550 ms~ 65% truthiness~ 25% truthiness *~ 10% truthiness **HTTP Quizthis is not a trick question…
- 3. “SPDY? We can’teven get HTTP right…”the why, how, and how-to of Goliath
- 4. ServerClient20 msTCP handshakeHTTPRequestheaders, body40 msprocessingMulti-part body (*)Terminate connectionHTTP 1.0RFC 1945 (1996)+ 40ms TCP setup (network)+ 20ms request (network) + 40ms processing + 20ms response (network)66% of time in network overhead
- 5. Benchmark client RTT,not just the server processing timeA public service announcement…
- 6.
- 7.
- 8. Default to “on”PipeliningNomultiplexing
- 9. Parallel requestsHTTP 1.1RFC2616 (1999)
- 10. + 40ms TCPsetup (network)+ 20ms request (network) + 40ms processing + 20ms response (network) x 40ms TCP setup (network)+ 20ms request (network) + 40ms processing + 20ms response (network) 200ms for two requestsSmall win over HTTP 1.0Keep-aliveRFC 2616 (1999)* One gotcha…
- 11. Net:HTTPKeep-aliveRFC 2616 (1999)Connection:close < ugh!
- 12. + 40ms TCPsetup (network)+ 20ms request (network) + 40ms processing + 20ms response (network) 60% of time in network overhead120ms for two requests – 50% improvement!PipeliningRFC 2616 (1999)
- 13. Connection setup: 50msRequest1: 300msRequest 2: 250msTotal time: ~250 ms~300 ms~350 ms~600 msPipelining Quiz RFC 2616 (1999)
- 14. There is justone small gotcha… Making HTTP Pipelining Usable on the Open Webhttp://tools.ietf.org/html/draft-nottingham-http-pipeline-01
- 15. conn =EM::HttpRequest.new('http://gogaruco.com')r1 =conn.get:path => "speakers.html", :keepalive => true# 250 msr2 =conn.get :path => "schedule.html"# 300 msTotal execution time is:250 ms300 ms550 msKeep-alive what? HTTP 1.0!~ 65% truthiness~ 25% truthiness *~ 10% truthiness **Good: Keep-alive + PipeliningBad: Keep-alive + Garbage“I’m confused”HTTP in the wildit’s a sad state of affairsKeep-alive: mostly works – yay!Pipelining: disabled (except in Opera)
- 16. HTTP can bea high-performance transportGoliath is our attempt to make it work
- 17. Goliath == v3API stack
- 18. Open source in2011
- 19.
- 20.
- 21.
- 22.
- 23. 95%+ of trafficvia API’s++Brief HistoryGoliath @ PostRank
- 24. Rails…HTTP APIHTTP APIHTTPAPIHTTP APISQLSQLSQL…SQLSQLSolrSQLSeparate logical & physical services
- 25. Easy to tune,easy to maintain, easy to “scale”
- 26. Stable code, fault-tolerancePROHigherupfront ops cost
- 27. Lots of cross-servicecommunicationCON
- 29.
- 30. AsyncHTTP response streaming+ progressive notifications
- 31. AsyncHTTP request streaming+ progressive notifications
- 32. Multiple requests withinthe same VM
- 33.
- 34.
- 35. Ruby API &“X-Ruby friendly”
- 36. Easy to maintain& test… lower ops costs… full HTTP 1.1 support… Ruby polyglot!
- 37. Client API(optional) Fibersoptionalasync“Sync API”RoutingMiddlewareasync-rack0.3 ms(streaming) HTTP ParserRuby, JRuby, Rubinius …HTTP 1.1 EventMachineNetworkGoliathOptimize bottom up + minimal client API
- 38.
- 39. require'goliath'classHello< Goliath::APIdefresponse(env) [200, {}, "Hello World"]endend$>ruby hello.rb-sv –p 8000 –e productionHello WorldSimple Goliath server
- 40. classHello< Goliath::API use Goliath::Rack::Params use Goliath::Rack::JSONP use Goliath::Rack::Validation::RequestMethod, %w(GET) use Goliath::Rack::Validation::RequiredParam, {:key => 'echo'}defresponse(env) [200, {}, {pong: params['echo’]}]endendMiddlewareNo rackup file
- 41. classBonjour< Goliath::APIdefresponse(env) [200, {}, "bonjour!"]endendclassRackRoutes< Goliath::API map '/version'do run Proc.new { |env| [200, {}, ["Version 0.1"]] }end get "/bonjour", Bonjournot_found('/') do# run Proc. new { ... }endendRoutingsimple, but powerful
- 42. classAsyncUpload< Goliath::APIdefon_headers(env, headers)env.logger.info'receivedheaders: '+headersenddefon_body(env, data)env.logger.info'received data chunk: '+ dataenddefon_close(env)env.logger.info'closing connection'enddefresponse(env)# called when request processing is completeendendAsync Request Processingdon’t need to wait for the full request…
- 43. classStream< Goliath::APIdefresponse(env)pt=EM.add_periodic_timer(1) {env.stream_send("hello") }EM.add_timer(10) dopt.cancelenv.stream_send("goodbye!")env.stream_closeendstreaming_response 202, {'X-Stream' => 'Goliath’} endendAsync/Streaming Responsedon’t need to render full response…
- 44. * Goliath::SPDYclassWebsocket< Goliath::WebSocketdefon_open(env)env.logger.info”WebSocketopened” enddefon_message(env, msg)env.logger.info”WebSocket message: #{msg}” enddefon_close(env)env.logger.info”WebSocket closed” enddefon_error(env, error)env.logger.error errorendendWeb-Socketssimple backend extension
- 45.
- 46. defresponse(env) conn =EM::HttpRequest.new(’http://google.com/') r1 =conn.get :query => {:q => 'gogaruco'} r1.callback do r2 =conn.get :query => {:q => 'rubyconf'} r2.callback { ... } r2.errback { ... }end r2.errback { ... }streaming_response 200, {}endAsync fun{ { {} } } …
- 47. defresponse(env) conn =EM::HttpRequest.new(’http://google.com/') r1 =conn.get :query => {:q => 'gogaruco'}if r1.error? r2 =conn.get :query => {:q => 'rubyconf'}else# ...end[200, {}, r2.response]endAsync + FibersRuby gives us a choice
- 48.
- 49.
- 50.
- 51.
- 52.
- 53.
- 54.
- 55.
- 56.
- 57.
- 58.
- 59.
- 60. …multi =EventMachine::Synchrony::Multi.newmulti.add :a,db.aquery("select sleep(1)")multi.add :b, db.aquery("select sleep(1)")res =multi.perform
- 61. describe HttpLogdo it 'forwards to our API server'dowith_api(HttpLog, api_options) do |api|get_request({}, err) do |c|c.response_header.status.should== 200c.response_header[’X-Header'].should =='Header'c.response.should=='Hello from Responder'endendendendIntegration Testingsimple end-to-end testing
- 62.
- 63.
- 64.
- 65. Examples: GIT repo/ examplesthoughts, questions?now or later: ilya@igvita.com