4 ms·
Yep, we run everything on AWS as of a few months ago. We've got a post about the nuts and bolts of that here: http://dev.mixrad.io/blog/2014/09/19/Migrating-Mix
by tcoupland 12y ago
Yep, we run everything on AWS as of a few months ago. We've got a post about the nuts and bolts of that here: http://dev.mixrad.io/blog/2014/09/19/Migrating-MixRadio-Infrastructure-To-AWS/ http://dev.mixrad.io/blog/2014/09/19/Migrating-MixRadio-Infr.... We've got a post about our deployment tools that's going to be going up soon!
In terms of data analysis we use a lot of Cascalog, although a fair amount of ad-hoc work is done in RedShift.
- nextos 12y agoInteresting! Just three more little things: - Do you document using Marginalia or something similar (perhaps lein-midje-doc)? - Since you do a lot of REST, have you ever considered Liberator? - Regarding Clojure books, I've found Clojure in Small Pieces quite interesting---but far from complete
- tcoupland 12y ago- We still havn't really hit on a solution for internal documentation. I'm something of a heretic on this point to be honest, as i try to actually deliver the 'code as doc' idea, which i think you can realize with a combination of compojure routes and schema definitions. - We did look at Liberator a while ago, but it didn't seem mature at the time. To be honest we get by perfectly find with compojure, having created our own middleware to deal with any fiddly bits. - The Joy of Clojure, for me, is the one. It's focus is on why Clojure is such fun to work with and doesn't get bogged down in trying to teach you every little function, it's not a reference book. A good read of that, coupled with the clojure cheatsheet, mix in 'The Little Schema' to get you lisping and then practice (4clojure, exercism.io, euler), which is key.
- vassilevsky 12y agoRunning everything in AWS doesn't seem very Microsoftish...