Re:Scoop: A Glimpse Into the NYTimes CMS
by burritofanatic on Tuesday June 17, 2014 @05:50PM
(#7907242)
I was always under the impression that they're Django/Python. Can anyone confirm?
[ Parent
| on HN ]
No.
We use a pretty normal ("boring") Java stack with Spring, Hibernate and Jersey. Some of the older components use Struts + JSPs whereas the newer components use Backbone (and related libraries).
Which database? A JDBC one?
Re:Scoop: A Glimpse Into the NYTimes CMS
by lvnenchak on Wednesday June 18, 2014 @02:52PM
(#7911923)
scoop uses mysql for its managed repository. we also use mongodb for our published repository that serves our apis to everybody else.
The NYT devs consist of several dev groups and a mix of stacks...some which are business-facing/product, and others that are in editorial (i.e. interactive news graphics). On the editorial side, they are one of the few in the news business that were using Ruby/Rails (the vast majority of newsrooms use Python/Django). There's also obviously a primarily-JavaScript group.
Re:Scoop: A Glimpse Into the NYTimes CMS
by superchink on Wednesday June 18, 2014 @03:18PM
(#7912115)
See krishy's comment above. It looks like they do not use Ruby/Rails for the CMS for editors, but use Java instead.
Right...I should've clarified...by "editorial", I meant the team that focuses on the public facing news projects, such as Derek Willis's campaign finance apps and utilities (http://itemizer.herokuapp.com/)...I don't think they do a lot of monolithic-type Rails apps currently, though, at least compared to client-side-heavy projects