Jeremy Walker has been using Rails since 2005. He is the CTO of Meducation - an educational social-network for medics - and runs his own software consultancy. He is a maintainer of various open source projects, including Propono, Larva and Inqusitio. You can follow Jeremy on Github and Twitter, and read more about him at his website.
The concept of the “monorail” is long established in the Ruby world – a large Rails application that does everything and quickly becomes cumbersome and overbearing. Developers that have find themselves in this situation are now looking for a better way to work.
Last year, my team at Meducation decided to split our “monorail” into a serivce-oriented architecture. Over the last 12 months, we’ve been breaking it apart and now have 21 different applications that work together. Each service has very seperate concerns and knowledge.
This entry is part 3 of 3 in the series Techniques to Secure Your Website with Ruby on RailsThis is the final part of our exploration into the Rails security. Last week we looked at mass-assignment and SQL injection issues, having previously explored the risks of session hijacking. This week we’ll look at risks to […]
This entry is part 2 of 3 in the series Techniques to Secure Your Website with Ruby on RailsLast week we looked at ways malicious people can try and hijack the sessions of valid users. This week, we’re going to look at two dangers you are faced with when a malicious user signs up to […]
This entry is part 1 of 3 in the series Techniques to Secure Your Website with Ruby on RailsDuring the seven years I’ve been using Rails, the framework has exploded in popularity because it’s made creating powerful applications quick and easy. It seamlessly handles so many of the issues that used to absorb developers’ time, […]