talk-scaling-a-large-monolithic-rails-app

https://www.youtube.com/watch?v=naTRzjHaIhE

at 3038 shadow proxy server

276 gems

at 7:40 rake stats

gem-database-rewinder

html 200 ms

api 80 ms

28 minutes "chanko" 'unit' has model, view, controller (those units sound a lot like what I might call features in 'facets') gem-chanko

talk-scaling-a-large-monolithic-rails-app#side-by-side-testing1 At 29:57 he talks about how they upgrade (side by side testing): https://www.youtube.com/watch?v=naTRzjHaIhE&t=29m57s

He talks about saving the HTTP responses returned by the current version of Rails and diffing them with the HTTP responses returned when they update the version of Rails. It's a black box test, where the externally facing behavior of the current version of the app becomes the gold master, and the new version of the app must have the same external behavior.

talk-scaling-a-large-monolithic-rails-app#side-by-side-testing1

Save response body in after :each (seems similar to our concept of checking for system health after each spec)

Referring Pages

rails-facets previous-interface-as-gold-master

People

person-akira-matsuda