Ruby is an interesting language in that it supports the use of multiple paradigms. One of these is the functional paradigm. In this series, we’ll visit each of these features one by one, and look at how you can use them to produce cleaner, more efficient, and better-structured code.
A couple of weeks ago, I wrote about Ruby Heroes. I thought I’d write a post about my Ruby Hero: Konstantin Haase. He is one of the busiest people I know in the Ruby community. His output is amazing – just check out his github profile!
As the Ruby community matures and our applications grow, we seek new ways to manage complexity, reduce coupling, and improve scalability. Though REST services are a good solution for a broad spectrum of problems, the temporal coupling is becoming harder to manage. In this article we look into messaging options.
SOA, or Service-Oriented Architecture, is often tossed around as an enterprise-only term, used by companies no smaller than Amazon. Fear not, SOA can be used by the Little Guys too! Let’s break the mold.
The Loccasions application now allows most of the basic functionality that I wanted to produce. Now it’s time to examine what went right, what went wrong, and what the next iteration is.