Rails articles by our experts
Scopes must return the
Nov 13, 2018
We’ve had another amazing RRUG meeting - the sixteenth one, and we’re sure there are many more to come. Once more, iRonin had the pleasure of sponsoring the event. This time, the presentations touched upon the often underestimated rake tasks, and the mistakes developers make that lead to very unhappy testers. Read on to learn more!
Using Policy Objects helps to keep your code clean, tight, and most of all, correct. Today’s blog post walks through Policy Object solutions used in a large Ruby on Rails application. Check it out!
Node.js and Ruby on Rails are two excellent choices for companies developing web-based applications. In most cases, either one of these two technologies will do the job. Ruby on Rails has recently been cited as the better option for smaller projects and teams, when speed of development and time to market are the most crucial aspects. Node.js can often do better when a large team wants to work on a project simultaneously by dividing it into modules, and to improve performance in specific cases. And sometimes, it’s the other way around. This article contains a breakdown of the main advantages and disadvantages of Ruby on Rails and Node.js, to help CEOs and startup founders decide which technology will better serve their business.
An MVP, or a Minimum Viable Product, is the initial version of a new product that consists only of the most essential features. Its goal is to work well enough for early adopters while allowing the development team to gather insights and user feedback, locate issues as well as identify the most valuable features. Once the concept has been proven and the product has been adjusted to fit the market reality, development can move forward at much less risk. If you’re not convinced, this article will list why building an MVP is a good idea and how to leverage Ruby on Rails to do so efficiently.
Oct 15, 2018
Another fantastic RRUG meeting is behind us! We had the opportunity to sponsor the recent edition of the Rzeszów Ruby User Group meetup, which is a wonderful, welcoming community for all Ruby fans in the area. Join us next time for interesting presentations and the opportunity to spend time with like-minded developers.
Oct 3, 2018
If you’re looking for a Ruby on Rails development team, you likely know RoR’s advantages. It’s a great back-end framework for rapidly developing robust web apps. Thanks to how mature both the community and the technology are, Rails resources (most iconic of which are its libraries, called gems) are stable and trustworthy. Instead of writing a user registration feature from scratch, developers can focus their attention on what makes the project truly unique. And on top of all that, Rails’ testing culture and support are excellent.
Knowing this, what you need next is to find the experts that’ll help you leverage Rails’ strengths.
Do you know what Airbnb, GitHub and Kickstarter have in common? Their websites are built with Ruby on Rails, a well-known and much-loved back-end framework. Though widely used for large-scale projects, Rails offers a particular advantage to startups, as it allows for rapid development and helps shorten time-to-market while maintaining high code quality. Rails is a web framework for the programming language Ruby, which has been around since the mid 1990s and is still popular among developers. Its main rivals in the world of web development are Python and PHP, and in this article, we’d like to take a closer look at the advantages and disadvantages of these three technologies.
Aug 29, 2018
Software as a Service (SaaS) projects face many unique challenges during development. Teams working on SaaS products need to focus on scalability, to make sure new modules and functionalities can be built easily as the platform develops and customers present special requirements. They need to be able to test their code easily and deliver a high-quality experience to enterprise clients. Thankfully, Ruby on Rails is a technology that helps SaaS companies solve many of these issues.
Ruby on Rails is a fantastic technology for startups developing their web products. It offers a high speed of development, which allows for rapid creation of an MVP and shortens time-to-market. Ruby’s many libraries (gems) available to developers mean that the team doesn’t have to reinvent the wheel when solving problems - they can use ready-made solutions and save time.
Integrations can oftentimes be a challenge to implement. Every system and website is different, with a unique internal architecture, capabilities and limits. Because of this, integration might require writing separate code for each system, as was the case for one of iRonin’s clients, an employee referral system used by many companies on their unique websites.
Test-driven development can be the saving grace of startups and small companies, allowing them to save time and money, and deliver much sleeker apps to users. If your new product is full of bugs, how likely is it that early adopters will stick with it and promote it among friends? Not very. This is why early testing is 100% worth the investment. Find out how to implement it without making the 5 most common testing mistakes.
Aug 10, 2018
Out of the many popular backend web technologies out there (like Node.js, Django and Laravel), many startups are choosing Ruby on Rails, a mature framework created in 2004. Why haven’t they moved on to something more modern and exciting? The answer is simple: because Ruby on Rails works, and it works fast. And here’s why.
Recently, we had an interesting request from one of our clients where we needed to implement time travel for testing purposes - or fake time travel at least! The Quality Assurance (QA) team of one of our clients wanted to test functionality under particular time constraints within their application. To do that, they needed is to move the application’s internal clock to check and see whether some these time-based actions were allowed or forbidden (depending on the case). Mocking up operating system’s datetime settings on Heroku was the answer, with setting up environmental variables for datetime testing. Heroku datetime testing in a Ruby on Rails application required a little configuration - but we were able to get the job done.
Jul 13, 2018
Are you using Datadog and Heroku? Would you like to send your Ruby on Rails application’s logs to Datadog for history purposes and easier processing? We will show you how to do it.
Mar 30, 2018
It’s that time again… the weekend of 16-18th March was time for iRonin Ruby on Rails developers to get excited and head to Wroclove.rb - the most prominent event in the Ruby community, that we have been supporting since 2015. It is almost a company tradition to visit Wroclaw and participate in this amazing event for Ruby enthusiasts and developers. Check what our top Ruby developers have to say about this event.
Design patterns in large Ruby on Rails web applications: constructing a Query Object class that is responsible for elegantly querying a database. Read our blog post to find out how to make a simple and easy to test Query Object implementation within a Rails application.
Mar 16, 2018
It’s time to get started with Part 4 of our GraphQL series. This time we will build an API with Ruby on Rails. This will provide the same features and functionality as an API built with Node.js, as we covered in part 2.
Jun 28, 2017
In the super critical sphere of fin-tech web app development, there’s no room for mistakes. Find out in our case study of a Ruby on Rails US Lease Management System the best practices for dealing with systems where customers real money is at stake in every line of code, every piece of the infrastructure, and in every hour of the day.
Mar 22, 2017
Mar 3, 2017
Working correctly with database indexes is always the key to application performance and reliability. Especially when the amount of data grows rapidly, well designed database architecture really pays off. However, when we’re working with database indexes, it can be easy to miss something, or fall into the trap of a tricky outlying case. One of these is when performing unique indexing on multiple columns, where at least one of them is null.