Blog

Search This Blog

Loading...

Wednesday, October 30, 2013

Iron.io @ DevBeat 2013 (talking about Go)

DevBeat 2013 - Nov 12-13th
Iron.io be at the DevBeat 2013 conference in San Francisco on Nov 12-13th. It's a great conference for experienced developers and includes a number of top developer speakers – including Travis Reeder, Iron.io's CTO.

Travis will be talking about Iron.io's use of Go in production. It's been two years from what at the time was a risky move. It's turned out, however, to be a very good decision (as detailed here and here). Travis will expanding on the reasons why and will go in-depth on why we, and many others, believe Go will be powering many of the high-scale cloud applications and services of the future.
DevBeat 2013 
DevBeat is a prime event for experienced developers who are looking to expand their knowledge into new areas – new languages, security, hardware, and team management.   
Speakers include:
• Tim Bray, Dev Advocate, Google
• Tom Preston-Werner, Co-Founder & CEO, GitHub
• Richard Stallman, Founder, Free Software Foundation
• Rasmus Lerdorf, Creator, PHP
• David Heinemeir Hansson, Creator, Ruby on Rails
• Raymond Camden, Senior Developer Evangelist, Adobe
Travis Reeder, Co-Founder & CTO, Iron.io
• Jeff Lawson, Co-Founder and CEO, Twilio
• Alex Payne, Programmer, Writer & Angel Investor
• Jonathan LeBlanc, Principal Developer Evangelist, PayPal
• Eric Minick, DevOps Evangelist, IBM
• See them all here 
Agenda – Tuesday, November 12th

Travis will be there most likely in an Iron.io t-shirt. Look for him if you want to talk about message queueing, async processing, or Go. (Or just get on a list for the next run of t-shirts.) (@treeder)



Special Offer: If you're interested in going, be sure to use the coupon code GoSF and get 20% off:

Monday, October 28, 2013

IronSharp — .NET Client Library for Iron.io (a contribution from a user)

IronSharp is a great new contribution from a long-time supporter and user of IronMQ, IronWorker, and IronCache.

Jeremy Bell created IronSharp to provide updated access in .NET to all Iron.io services. It's a simple solid library that wraps the API calls for IronMQ, IronWorker, and IronCache and includes support for the latest Iron.io features. (It also has a great logo and GitHub page.)

The .NET community is huge force in application development and in cloud computing. And while Iron.io has existing libraries for .NET, IronSharp is an up-to-date addition that is bound to surpass them in popularity and find many fans and adherents.

About the IronSharp Creator

Jeremy Bell is top .NET developer and principal architect at Terryberry Company. He lives in Grand Rapids, MI and his github handle is grcodemokey.





–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

.NET Interface for IronMQ

.NET Interface for IronWorker
.NET Interface for IronCache

We're grateful for the contribution (and the great logo!).

Monday, October 7, 2013

IronCast 4: How to connect to your database from IronWorker - IronWorker 101 Part 4/4

In a series of four IronCasts, we will provide a high-level introduction to using IronWorker, an easy-to-use scalable task queue. In this series, we will be using an example application which is written in Rails. However, the same concept applies to every language or framework.

In this video, we will show you how to connect to your database from IronWorker.



One of the frequent questions that we get asked at Iron.io is how to get your workers to write back to the database, especially in development.

Step 1 - Creating a cloud hosted development database:
IronWorker on EC2 needs an open port to your database, and your database credentials in order to connect to your database. So no matter what language or framework, those are the two small requirements in order for your workers to connect to your DB. So the easiest way to do this is in development is by using a cloud hosted development database. It is generally harder to open a port (that a worker on EC2 can access) to the database on your local machine.

Using heroku as an example, you can create a free heroku development database:
heroku addons:add heroku-postgresql:dev

Step 2 - Passing your database credentials into the payload:
def create
  @snippet = Snippet.new(snippet_params)
  if @snippet.save
    @client ||= IronWorkerNG::Client.new(:token => ENV["TOKEN"], :project_id => ENV["PROJECT_ID"])
    @client.tasks.create("pygments",
                         "database" => Rails.configuration.database_configuration[Rails.env],
                         "request" => {"lang" => @snippet.language,
                                       "code" => @snippet.plain_code},
                         "snippet_id" => @snippet.id)
    redirect_to @snippet
  else
    render :new
  end
end
Step 3 - Connecting to your database using the credentials:
def setup_database
  puts "Database connection details:#{params['database'].inspect}"
  return unless params['database']
  # estabilsh database connection
  ActiveRecord::Base.establish_connection(params['database'])
end

And that’s it! Three simple steps and you have connected to your cloud hosted database from your IronWorker. Click here to take a more detailed look at the repository.

This is the end of the first series of IronCast. We have gone through various basic aspects of using an IronWorker such as writing worker files, prototyping locally and connecting to the database. Please don't hesitate to contact us if you have any suggestions to any topics that you would like to us to cover in future IronCasts.


Tuesday, October 1, 2013

Iron.io @ API:World 2013


Chad Arimura from Iron.io will be speaking at API:World this week. API:World 2013 is part of the DataWeek conference which is being held in San Francisco on Oct 2nd-3rd.

Iron.io @ API:World 2013
The API World conference was created with the mission to be a technology-neutral catalyst of connections, knowledge, trust, and business within the developer community of API providers and consumers. If you are a coder, a startup, or an enterprise that consumes or provides multiple APIs this is an event designed for you.





In a world of real-time data, real-time events, and real-time social interactions - it is becoming more and more critical that API's enable a "real-time web". What does a 'real-time web' mean, and what API-based technologies are core to this vision of the web? 
Moderators/Speakers
• Chris Ismael, Developer Advocate, Mashape (moderator)
• Chad Arimura, CEO / Co-founder, Iron.io
• Stephen Blum, Founder, PubNub
• James Tamplin, CEO / Co-founder, Firebase

Chad will likely be there in an Iron.io t-shirt and wearing his lucky boots. Look for him if you want to talk about message queuing, async processing at scale, Seattle Seahawks football, or playing in a band. (Or just get on a list for the next run of t-shirts.)