• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Ruby Meetup - Goliath - August 24th 2011
 

Ruby Meetup - Goliath - August 24th 2011

on

  • 2,244 views

Asynchronous web frameworks excel at integrating with external services and can offer higher throughput then traditional synchronous systems. However asynchronous programming is not without its ...

Asynchronous web frameworks excel at integrating with external services and can offer higher throughput then traditional synchronous systems. However asynchronous programming is not without its challenges and porting your existing codebase to an asynchronous platform may not be a viable option.

In this presentation Nolan will outline how you can RESTfully integrate an asynchronous framework named Goliath [ https://github.com/postrank-labs/goliath] with your existing infrastructure and external services enabling you to build scalable richer interactions.

Statistics

Views

Total Views
2,244
Views on SlideShare
2,240
Embed Views
4

Actions

Likes
1
Downloads
8
Comments
0

1 Embed 4

https://twitter.com 4

Accessibility

Upload Details

Uploaded via as Apple Keynote

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • So if we look at this code, we can see that we are requesting the document found on google.com, and lets say that there is some sort of problem parsing the dom so we raise an error stuff happens\n\n
  • so surprisingly here’s what’s printed out when this code runs, the callback is executed outside of the context of the error handler and any exceptions raised are unhandled\n
  • in ruby 1.9 fibers provide a way for us to untangle this callback spaghetti\n
  • so if we look at this code you will see we wrap the fetching of the document in a syncify function\n
  • so if we look at this code you will see we wrap the fetching of the document in a syncify function\n
  • so if we look at this code you will see we wrap the fetching of the document in a syncify function\n
  • \n
  • in ruby 1.9 fibers provide a way for us to untangle this callback spaghetti\n
  • rack middleware\n
  • so if we look at this code you will see we wrap the fetching of the document in a syncify function\n
  • so if we look at this code you will see we wrap the fetching of the document in a syncify function\n
  • for example facebook’s link scraper\n
  • for example facebook’s link scraper\n
  • for example facebook’s link scraper\n
  • so if we look at this code you will see we wrap the fetching of the document in a syncify function\n
  • for example facebook’s link scraper\n
  • This approach is useful for when you need to integrate external services with some part of your website/services user experience\n
  • This approach is useful for when you need to integrate external services with some part of your website/services user experience\n
  • so if we look at this code you will see we wrap the fetching of the document in a syncify function\n
  • so if we look at this code you will see we wrap the fetching of the document in a syncify function\n
  • Talk about me\n
  • right now our card auth’s happen in our passenger’s which are single threaded and blocking\nfibers would be a better solution to this problem and remove a point of failure from our systems\n

Ruby Meetup - Goliath - August 24th 2011 Ruby Meetup - Goliath - August 24th 2011 Presentation Transcript