In non trivial projects we often use SOA<\/a> approach. Definitely ActiveResource operations are much slower than ActiveRecord operations because first one use HTTP connection and second one use usually persistent<\/em> connection to database and database is usually always faster than application service.<\/p>\n\n\n\n But modern HTTP\/1.1 servers support persistent connection<\/a> and as Ilya Grigorik already mentioned in his awesome article<\/a> we can have serious speedup for resources usage.<\/p>\n\n\n\n The problem is that ActiveResource does not support keep-alive connections<\/a>.<\/p>\n\n\n\n But not for Railsware :).<\/p>\n\n\n\n\n\n\n\n After playing a bit with sources we released small gem ActiveResource::Persistent<\/a> that allows ActiveResource to use HTTP keep-alive feature.<\/p>\n\n\n\n Installation is trivial. Just drop line into your Gemfile<\/p>\n\n\n\n And all your resources will automatically reuse connections to services! Persistent connections are handled by excellent net-http-persistent<\/a> library. The gem actually is very simple and provides ActiveResource::Persistent::HTTP object wrapper for ActiveResource.<\/p>\n\n\n\n However we covered library with specs that ensure it will work with different ActiveResource versions.<\/p>\n\n\n\n Currently it works with:<\/p>\n\n\n\n Enjoy! :)<\/p>\n\n\n\n Preface In non trivial projects we often use SOA approach.Thereby one big monolithic application can be segregated into smaller applications or services. The benefit is obvious – it’s easy to control and maintain small applications. If you use Rails framework you probably already use ActiveResource for requesting your services because if follows ActiveRecord conventions. Definitely…<\/p>\n","protected":false},"author":19,"featured_media":1932,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[3],"tags":[],"coauthors":["Andriy Yanko"],"class_list":["post-1925","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-development"],"acf":[],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t
Thereby one big monolithic application can be segregated into smaller applications or services. The benefit is obvious – it’s easy to control and maintain small applications. If you use Rails framework<\/a> you probably already use ActiveResource<\/a> for requesting your services because if follows ActiveRecord conventions.<\/p>\n\n\n\nActiveResource is Persistent<\/h2>\n\n\n\n
Installation<\/h2>\n\n\n\n
gem 'activeresource-persistent', :require => 'active_resource\/persistent'\n<\/pre>\n\n\n\n
You should NOT modify any line of your code.<\/p>\n\n\n\nUnder the hood<\/h2>\n\n\n\n
References<\/h2>\n\n\n\n