Rails, building a versioned API. Try to keep it incredibly light weight with just VERBS applied to resources. Trying to avoid that word that starts with R and e

Rails, building a versioned API. Try to keep it incredibly light weight with just VERBS applied to resources. Trying to avoid that word that starts with R and ends with ESTful. I might use RBX or JRuby depending on what kind of and the amount background processing. Basically if I need native threads. For things that might be heavy and require both speed and massive concurrency I might switch that out to either Go or Erlang. In fact, for some portion of the APIs I suspect not to use ruby and instead Go/Erland. Depends basically on the situation. I will probably stick to SQL, PostgreSQL to be precise. For heavy relationships, I'd use Redis for associations. Keeping Model IDS in sets or orderedSets. That way I could just keep my SQL light weight and only need indexing the ids and avoid that whole mess of compound index. Memcache with Rack-Cache.. I'd suspect I'd rely heavily on HTTP Cache. That way I don't need to cache data objects, and have to redo the json all over again. Basically tring to avoid layers of caches, when I could just do it at the user end point. Of course I understand edge cases will turn up. So I'll be prepared for that. Then the client(s). iOS, just because I'm pretty certain whatever we offer, we can offer it better on the mobile platform as a native, also I can code OBJ-C & design for iPhone. Web, I'm probably not going to be doing the web-frontend much so I leave it to whoever I deem fit for the web. Whoever this person is, hen will be in charge of both the design as well as the code base for the web front-end. Meaning whatever stack hen choses to work with. Preferably Bourbon.io with SASS/SCSS and either Ember.js or Batman.js.