We've all heard the "Rails can't scale" myth, but how far can we scale Rails? This is a story about a one year project scaling a REST API for concert ticketing and ecommerce to huge presale events and the lessons learned on the way.
HTTP Caching on a Budget
Redis is Your Friend
Waiting Queue Architectures
How not to Blow up Your Database
How to Test Scale
Tips and Tricks for Concurrent Writing
A few years ago, I set out to improve my knowledge of security in web applications. It's not something I had much education in (at all!) and after an application I built was penetration tested, I knew I wanted to find out much more. I want to tell you about how I educated myself, a few things I've learned along the way, and how I've applied that to my day-to-day work as a Rails developer.
Although we might not be experts at it, general web application security knowledge is crucial for success in engineering teams. Penetration tests and bug bounties are useful, but your team is going to perform at a higher level if they can assess risks and mitigations before features even make it into the backlog. By keeping security in mind as you develop, you'll create higher-quality code that will save you from embarrassing or potentially disastrous mistakes.
So, if you've never thought too much about it, now's your chance to start learning about security, and start thinking about how your team can integrate it more into your daily workflow.