Ruby Patterns: Webservice object
16 Jul 2013This is a series about Ruby Patterns, which will explain some common uses of Ruby syntax. The second post is about a webservice based. I like to call it a pattern because it is very common and tends to repeat (on a not-duplicated way) on Service Oriented Architecture based applications. Of course, this code may be too sophisticated for such a small script like this, but it may be a good way to handle things on a more complex application.
So, you’re given the task to write a class that access a webservice and returns the info on it (e.g. the github repos for a given organization). A simplistic implemetation can be like this:
require 'faraday'
require 'json'
def retrieve_repos_for(org)
connection = Faraday.new(:url => 'https://api.github.com') do |faraday|
faraday.adapter Faraday.default_adapter
end
response = JSON.parse(connection.get("/orgs/#{org}/repos").body)
response
end
retrieve_repos_for('github').each do |repo|
puts repo['clone_url']
end
Obviously, this is an example of a procedural implementation, so, let’s make it more object oriented.
require 'faraday'
require 'json'
module Github
class Organization
def initialize(organization)
@organization = organization
end
def repos
connection = Faraday.new(:url => 'https://api.github.com') do |faraday|
faraday.adapter Faraday.default_adapter
end
response = JSON.parse(connection.get("/orgs/#{@organization}/repos").body)
response
end
end
end
Github::Organization.new('github').repos.each do |repo|
puts repo['clone_url']
end
Nice, we now have it inside a class. But we can extract some private methods here.
require 'faraday'
require 'json'
module Github
class Organization
def initialize(organization)
@organization = organization
end
def repos
response = JSON.parse(connection.get(repos_url).body)
response
end
private
def connection
Faraday.new(:url => 'https://api.github.com') do |faraday|
faraday.adapter Faraday.default_adapter
end
end
def repos_url
"/orgs/#{@organization}/repos"
end
end
end
Github::Organization.new('github').repos.each do |repo|
puts repo['clone_url']
end
Well, the public methods seems to be more concise now and we have extracted some methods that can be more easily reused. But there is a few flaws: if we call the repos method twice, it will make two requests, but this is easy to solve: just add some memoization.
require 'faraday'
require 'json'
module Github
class Organization
def initialize(organization)
@organization = organization
end
def repos
@repos ||= JSON.parse(connection.get(repos_url).body)
end
private
def connection
Faraday.new(:url => 'https://api.github.com') do |faraday|
faraday.adapter Faraday.default_adapter
end
end
def repos_url
"/orgs/#{@organization}/repos"
end
end
end
Github::Organization.new('github').repos.each do |repo|
puts repo['clone_url']
end
We’re almost done here. I’m not satisfied with the JSON.parse(connection.get(repos_url).body)
, it seems such a complex line. Let’s extract some methods here.
require 'faraday'
require 'json'
module Github
class Organization
def initialize(organization)
@organization = organization
end
def repos
@repos ||= get(repos_url)
end
private
def connection
Faraday.new(:url => 'https://api.github.com') do |faraday|
faraday.adapter Faraday.default_adapter
end
end
def get(url)
JSON.parse(connection.get(url).body)
end
def repos_url
"/orgs/#{@organization}/repos"
end
end
end
Github::Organization.new('github').repos.each do |repo|
puts repo['clone_url']
end
The repos
method seems simple enough now, and we have moved the parsing responsability to the get
method. But we can get rid of it delegating to someone else to do that.
There is a great gem called faraday-middleware that parses it for me, based on the content type header
and returns a hash, so, let’s use it.
require 'faraday'
require 'faraday_middleware'
module Github
class Organization
def initialize(organization)
@organization = organization
end
def repos
@repos ||= get(repos_url)
end
private
def connection
@connection ||= Faraday.new(:url => 'https://api.github.com') do |faraday|
faraday.adapter Faraday.default_adapter
faraday.response :json, :content_type => /\bjson$/
end
end
def get(url)
connection.get(url).body
end
def repos_url
"/orgs/#{@organization}/repos"
end
end
end
I’ve also added a memoization on the connection (we don’t need to instantiate a new one every time).
Two days later, a new requirement: get the organization info and add it on the api. This implementation makes it really easy:
require 'faraday'
require 'faraday_middleware'
module Github
class Organization
def initialize(organization)
@organization = organization
end
def repos
@repos ||= get(repos_url)
end
def info
@info ||= get(info_url)
end
private
def connection
@connection ||= Faraday.new(:url => 'https://api.github.com') do |faraday|
faraday.adapter Faraday.default_adapter
faraday.response :json, :content_type => /\bjson$/
end
end
def get(url)
connection.get(url).body
end
def repos_url
"/orgs/#{@organization}/repos"
end
def info_url
"/orgs/#{@organization}"
end
end
end
org = Github::Organization.new('github')
puts org.info['name']
org.repos.each do |repo|
puts repo['clone_url']
end
Neat! It is indeed really easy to add new endpoints support to our class. But I think it has a lot of responsability: it is dealing with the connection to the API. Let’s extract a new class that does that and refer to it on the client method.
require 'faraday'
require 'faraday_middleware'
module Github
class Client
def initialize
@connection = Faraday.new(:url => 'https://api.github.com') do |faraday|
faraday.adapter Faraday.default_adapter
faraday.response :json, :content_type => /\bjson$/
end
end
def get(url)
@connection.get(url).body
end
end
class Organization
def initialize(organization)
@organization = organization
end
def repos
@repos ||= client.get(repos_url)
end
def info
@info ||= client.get(info_url)
end
private
def client
@client ||= Github::Client.new
end
def repos_url
"/orgs/#{@organization}/repos"
end
def info_url
"/orgs/#{@organization}"
end
end
end
org = Github::Organization.new('github')
puts org.info['name']
org.repos.each do |repo|
puts repo['clone_url']
end
Now we have a pretty simple class, which I finally consider a final implementation, it splits the responsability to parse to another place and now I only have to specify the endpoints and get (or post/put/patch/delete) it. Another improvements may be to add a condition to do something when we have a 404 on an endpoint.
What about you ? Would you recommend another improvement ? Do you use something similar ?