Is your website ready for Black Friday traffic? Rails
Building and maintaining a complex infrastructure requires resources. So, what’s a startup to do? Expand its services. While some startups can bring on additional employees as needed, most lack the money and time it takes to afford such a luxury. Instead, these teams should consider the benefits of outsourcing their DevOps services.
I recently encountered a discussion in a developer chatroom about how to find good ruby gems to use for projects, and how to choose between them.
The (currently-defunct, hopefully only temporarily) website ruby-toolbox.com was mentioned, as well as awesome-ruby.com, and some conversation ensued about how to properly choose between similar dependencies for a given software requirement and why it's important.
Performance is a huge priority for any developer. However, people often don’t worry about performance until it starts to dip and there’s an immediate cause for concern. Performance needs to be something we focus on up front—not just when the walls come tumbling down. It needs to be part of the process, not something that’s reviewed occasionally.
In this post, we’ll consider a few things you can do to improve performance, starting with the database.
We’ve heard it again and again, like a nagging schoolmaster: Keep your Rails controllers skinny. Yeah, yeah, we understand. But that’s often easier said than done—because things get complex. And we need to talk to other parts of our codebase or to external APIs to get the job done.
Mailers. Stripe. External APIs. All that code starts to add up.
Many web developers work on the highest levels of abstraction when we program. And sometimes it’s easy to take things for granted. Especially when we’re using Rails.
Have you ever dug into the internals of how the request/response cycle works in Rails? I recently realized that I knew almost nothing about how Rack apps or middleware works—so I spent a little time finding out. Below are my findings.
There’s something magical about the way that Ruby flows from your fingertips. Perhaps that’s why it was once said that “Ruby will teach you to express your ideas through a computer.” And it’s most likely the reason that Ruby has become such a popular choice for modern web development.
Just as in other languages, there are numerous ways to say the same thing in Ruby. I spend a lot of time reading and nitpicking people’s code on Exercism. And I often see exercises solved in a way that could be greatly simplified if the author had only known a certain Ruby method.
From the start, Rails was praised for being the easiest way to get Ruby on the web. Not only has it solidified itself as the easiest option, it’s become the best. Since then, many other options have arrived, but Rails is still the de facto framework for Ruby developers.
On June 30, 2016, Rails 5.0.0 was released. Since then, Ruby has spent more than 4,100 commits to make things simpler for users. Additionally, it’s released numerous iterations, including Rails 5.1.2, which was released on June 26, 2017.
Let’s talk about the elephant in the room: Rails is great and is exactly what’s needed for large-scale production applications. It has history—and if you got started in Ruby working on the web, chances are Rails is what you’re most familiar with. All these things are a fair argument for Rails as the framework of choice for many projects.