LivingSocial's Technology Blog

[...] service-oriented set-up. The functionality of the entire system is to show deals (aka. ‘inventory items’) available in or near a given city. These items can also be organized by a ‘ [...]

[...] calls out to cities-service and tags-service for all city and tagging information on inventory items. small represented inventory items just have the Hyperlinked URI for their city and their [...]

[...] in our company’s business department thinks it’s a great idea to not ony show a list of inventory items filtered by category (know as ‘tags’ to us techies), but also allow for presenting the [...]

[...] This is the first in a series of seven posts on service-oriented architecture derived from a workshop conducted by Cloves Carneiro and Tim Schmelmer at Abril Pro [...]

[...] This is the third in a series of seven posts on service-oriented architecture derived from a workshop conducted by Cloves Carneiro and Tim Schmelmer at Abril Pro [...]

[...] This is the fourth in a series of seven posts on service-oriented architecture derived from a workshop conducted by Cloves Carneiro and Tim Schmelmer at Abril Pro [...]

[...] This is the fifth in a series of seven posts on service-oriented architecture derived from a workshop conducted by Cloves Carneiro and Tim Schmelmer at Abril Pro [...]

[...] architecture derived from a workshop conducted by Cloves Carneiro and Tim Schmelmer at Abril Pro Ruby. The series is called SOA from Day One – A love story in 7 parts. If you are like me, [...]

[...] architecture derived from a workshop conducted by Cloves Carneiro and Tim Schmelmer at Abril Pro Ruby. The series is called SOA from Day One – A love story in 7 parts. In the previous [...]

[...] architecture derived from a workshop conducted by Cloves Carneiro and Tim Schmelmer at Abril Pro Ruby. The series is called SOA from Day One – A love story in 7 parts. APIs will only be used when [...]

[...] architecture derived from a workshop conducted by Cloves Carneiro and Tim Schmelmer at Abril Pro Ruby. The series is called SOA from Day One – A love story in 7 parts. Service calls – when a [...]

[...] found in this branch of the inventory_service application Previous articles in this series: SOA Series Part 1: The What, the Why, and the Rules of Engagement SOA Series Part 2: SOA Sample Apps and [...]

This is the first in a series of seven posts on service-oriented architecture derived from a workshop conducted by Cloves Carneiro and Tim Schmelmer a [...]

This is the second in a series of seven posts on service-oriented architecture derived from a workshop conducted by Cloves Carneiro and Tim Schmelmer [...]

[...] .html page, as well as some URIs inside the API JSON specs. Previous articles in this series SOA Series Part 1: The What, the Why, and the Rules of Engagement SOA Series Part 2: Sample Apps and their [...]

[...] on service-oriented architecture derived from a workshop conducted by Cloves Carneiro and Tim Schmelmer at Abril Pro Ruby. The series is called SOA from Day One – A love story in 7 parts. If [...]

[...] on service-oriented architecture derived from a workshop conducted by Cloves Carneiro and Tim Schmelmer at Abril Pro Ruby. The series is called SOA from Day One – A love story in 7 parts. In [...]

[...] on service-oriented architecture derived from a workshop conducted by Cloves Carneiro and Tim Schmelmer at Abril Pro Ruby. The series is called SOA from Day One – A love story in 7 parts. APIs will [...]

[...] on service-oriented architecture derived from a workshop conducted by Cloves Carneiro and Tim Schmelmer at Abril Pro Ruby. The series is called SOA from Day One – A love story in 7 parts. Service [...]

[...] a series of seven posts on service-oriented architecture derived from a workshop conducted by Cloves Carneiro and Tim Schmelmer at Abril Pro Ruby. The series is called SOA from Day One – A love [...]

[...] a series of seven posts on service-oriented architecture derived from a workshop conducted by Cloves Carneiro and Tim Schmelmer at Abril Pro Ruby. The series is called SOA from Day One – A love [...]

[...] of seven posts on service-oriented architecture derived from a workshop conducted by Cloves Carneiro and Tim Schmelmer at Abril Pro Ruby. The series is called SOA from Day One – A love [...]

[...] of seven posts on service-oriented architecture derived from a workshop conducted by Cloves Carneiro and Tim Schmelmer at Abril Pro Ruby. The series is called SOA from Day One – A love [...]

Hash#map can loop through key/value pairs to return an Array of the return: [...]

Fun with Array: [...]

Use Code Blocks to Extract Ceremony: Often in code, there are things we have to do over and over, varying some small behavior in the middle of the op [...]

Using default_proc to deeply, arbitrarily nest new Hash: While I wouldn’t do this in real life, default_proc is a nice method to know about. Feel f [...]

This is the second in a series of seven posts on service-oriented architecture derived from a workshop conducted by Cloves Carneiro and Tim Schmelmer [...]

[...] : SOA Series Part 1: The What, the Why, and the Rules of Engagement SOA Series Part 2: SOA Sample Apps and Their Development and Deployment Flow SOA Series Part 3: Documenting and Generating [...]

[...] series SOA Series Part 1: The What, the Why, and the Rules of Engagement SOA Series Part 2: SOA Sample Apps and Their Development and Deployment Flow SOA Series Part 3: Documenting and Generating Your [...]

[...] series SOA Series Part 1: The What, the Why, and the Rules of Engagement SOA Series Part 2: SOA Sample Apps and Their Development and Deployment Flow SOA Series Part 3: Documenting and Generating Your [...]

[...] Previous articles in this series SOA Series Part 1: The What, the Why, and the Rules of Engagement SOA Series Part 2: Sample Apps and their Development & Deployment Flow [...]

[...] articles in this series: SOA Series Part 1: The What, the Why, and the Rules of Engagement SOA Series Part 2: SOA Sample Apps and Their Development and Deployment Flow SOA Series Part 3: [...]

[...] Previous articles in this series SOA Series Part 1: The What, the Why, and the Rules of Engagement SOA Series Part 2: SOA Sample Apps and Their Development and Deployment Flow SOA Series Part 3: [...]

[...] Previous articles in this series SOA Series Part 1: The What, the Why, and the Rules of Engagement SOA Series Part 2: SOA Sample Apps and Their Development and Deployment Flow SOA Series Part 3: [...]

[...] library to use the actual HTTP service-based backend instead (which is the default for our client gem anyway). Customizing mocks To serve the needs of special-case, non-standard situations, the [...]

[...] article lays out a few things we learned when considering these points: Build caching into your client gem Often the team that builds a service will also be developing the libraries (e.g., Ruby client [...]