SOA applications in Rails

Few useful resource for better understanding SOA design with Ruby on Rails

  1. embed Completed

    Service-Oriented Design with Ruby and Rails

    <span>Ruby on Rails deployments are growing, and Rails is increasingly being adopted in larger environments. Today, Rails developers and architects need better ways to interface with legacy systems, move into the cloud, and scale to handle higher volumes and greater complexity. In&nbsp;<b><i>Service-Oriented Design with Ruby and Rails</i>&nbsp;</b>Paul Dix introduces a powerful, services-based design approach geared toward overcoming all these challenges. Using Dix’s techniques, readers can leverage the full benefits of both Ruby and Rails, while overcoming the difficulties of working with larger codebases and teams.</span><span>&nbsp;</span>

    Edit Remove Move
  2. embed Completed

    SOA on Rails

    Edit Remove Move
  3. embed Completed

    Refactor Your Monolithic Rails App to a SOA

    Edit Remove Move
  4. embed Completed

    Restful Web Services

    <span>You've built web sites that can be used by humans. But can you also build web sites that are usable by machines? That's where the future lies, and that's what&nbsp;</span><i>RESTful Web Services</i><span>&nbsp;shows you how to do. The World Wide Web is the most popular distributed application in history, and Web services and mashups have turned it into a powerful distributed computing platform. But today's web service technologies have lost sight of the simplicity that made the Web successful. They don't work like the Web, and they're missing out on its advantages.</span><br>

    Edit Remove Move
  5. article Completed

    SOA for the Little GuysRubySource

    The goal of any SOA implementation is to segment portions of an application by logical and business functions. It can break down monolithic applications into many smaller, consumable services. SOA can be used by the Little Guys, but it’s generally not something you want to apply until experiencing growing pains. There’s no cut-and-dry answer to when SOA should be used, but database inefficiency, team scalability issues, deployment pains and unmanageable complexity are all key indicators. Smaller teams might want to use SOA in hopes of easier maintenance, faster iterations, more robust tests, and scalability.

    Edit Remove Move
  6. video Completed

    Rails services in the walled garden

    <span>In typical service oriented architectures, monolithic applications are sliced along domain verticals to create several independently evolving 'services' that can be used in combination to achieve various outcomes. Rails applications lend themselves to this architecture beautifully and are slowly making inroads in big organisations for this reason. One of the big problems with this approach is that analyzing and managing large quantities of data from multiple services to produce a result becomes very hard. What was originally a relatively simple task when all data sat in the same database as part of a monolithic application, becomes, when split into multiple services, a whole different beast. This talk will focus on our experiences building a system involving about a dozen rails based services integrated over HTTP and XML and the issues we had to deal with when working with large data sets.</span>

    Edit Remove Move

Continue learning by following more paths or create your own. Join for FREE

By clicking 'Get Started Free' you agree to our Terms of Service and Privacy Policy