Why application health is important in Ruby on Rails

A healthy Rails application is an asset that will benefit your organization for years to come - an unhealthy one, on the other hand, will be a weight you and your team will have to bear every day.

Why application health is important

A Rails application's health is important for a number of reasons.

1. Software can be an asset for your company.

Not in the platitude sense like "our people are our most valuable asset", but an actual asset: something that helps your business create more money. Something that your business can sell to someone else.

For some companies, their software can even be an asset that makes them unique and stand apart from their competitors. Think about FedEx's routing software and how hard it must work to make their operations function day and night.

Or take something even simpler: my local coffee shop switched to using Square to process credit cards. They didn't need a custom-programmed cash register anymore, and just used iPads with the Square card reader. It doesn't seem like a huge deal until you compare it to another shop that still does everything manually. This manual shop has to enter prices manually: 50% of the time they charge different amounts for the same drink, or they forget to add an extra charge for a change. Even minor sums like $0.50 per transaction can add up over time with the volume of transactions done, and cost you dearly.

2. Investing in your software assets can improve their performance

When you have a working asset, you want to continue its cashflow for as long as possible. Very few assets can keep working forever though: many of them wear out and have ongoing costs, others become obsolete and have to be discontinued.

Software can be different.

Software's ongoing costs can be extremely low based on what you get out of it. Once developed and in production, many Rails applications can continue working with a small operating budget for servers and a moderate budget for software maintenance.

Compare that to some machines that need millions spent on maintenance work each year just to continue working. That size of maintenance budget for a healthy software application is unnecessary.

3. Problem applications can cause negative ROI

On the other hand, if you don't have a healthy Rails application, your costs are going to be much higher. An unhealthy software application can eat money faster than an unfed teenager at a buffet.

With software, you're fighting two battles: one to improve the application, and one to repair the application from past decisions.

Making a healthy application from the start will need less repairing, and your investments can go towards improvements instead. An unhealthy one will need a lot of repair work - sometimes so much that it doesn't move forward at all.

Ongoing process

A Rails application needs maintenance and repair to keep working, much like any other asset. However, it can also be optimized to achieve an even greater return.

Before you can enhance the return, you need to make sure your application's health is high, and that it stays that way. Make sure the application's life is as long as possible and you don't lose the current return.

If you'd like to talk to me about your Rails application's health, I'd be happy to provide a free consultation to go through my multi-part evaluation process. To start, go here and enter your name, email address, and a short description of your application. I'll then contact you for more information.

To your application's health,

Eric Davis
Little Stream Software