Focus

Ruby

Ruby is a dynamic programming language designed for readable code, simple abstractions, and productive software development.
Learn more Get in touch

Develop software with Ruby

Ruby is an object-oriented, dynamically typed programming language with a strong focus on readable and expressive code. It is particularly well known for the Ruby on Rails web framework, but is also used for APIs, automation, and other server-side applications. The right language and framework depend on the system and its requirements. Through Software Architecture and Development, INNOQ therefore evaluates technologies in the context of architecture, team capabilities, and long-term evolution.

On this page, you will find articles, podcasts, and talks on Ruby, Ruby on Rails, and software development.

Our Services

We advise honestly, think innovatively and love to build. The result: successful software solutions, infrastructures and business models.

Learn more

Blog Posts

Blog Post

Marrying Rails, Turbolinks and JavaScript Custom Elements

Robert Glaser Alumnus
Blog Post

Building Component-Based Front Ends with Rails

Frederik Dohr Senior Consultant
Lucas Dohmen Alumnus

Talks

Talk
Talk

Git In My SQL’s Stead

Ruby Usergroup Berlin July 2020 / 19:00 - 21:00

Talk
Talk

That Looks Oddly Familiar

Ruby Usergroup Berlin March 2019 / 19:00 - 20:00

Talk
Talk

Property-based testing: You won’t look at your tests the same way ever again

GrillRB 2018 / 16:45 - 17:25

Primers

Primer

The Rails 7 Way

The Rails™ 7 Way is the comprehensive, authoritative reference guide for professionals delivering production-quality code using modern Ruby on Rails. It illuminates the entire Rails 7 API, its most powerful idioms, design approaches, and libraries. Building on the previous editions, this edition has been heavily refactored and updated.

Case Studies

Case Study

SACAC optimizes the quotation process with a customized software solution

Read case study
Case Study

User-friendly and mobile-first: Our SaaS solution for travel expense accounting

Read case study

Popular Topics

Frequently Asked Questions

Do you have questions about Software Architecture and Development? Here you will find answers to questions we are frequently asked.

When does a software project need architectural change rather than just new features?

If changes regularly cause unexpected side effects, releases become increasingly risky, or teams spend more time coordinating and maintaining systems than evolving them, the underlying issue is often architectural. That is when it makes sense to examine the system structure itself and identify which dependencies, boundaries, or technology decisions are slowing development down.

INNOQ supports teams both in assessing existing systems and in evolving them: Software Architecture and Development and Software Reviews

When is custom software a better choice than off-the-shelf software?

Custom software makes sense when core business processes or products are too specific to be supported effectively by standard software, or when extensive customization would be required over the long term. It is particularly relevant when software itself provides competitive differentiation or forms a key part of the business model.

INNOQ develops custom software from domain design and architecture through implementation and operation, while integrating it into existing system landscapes: Software Architecture and Development

How do you choose the right technology stack for a software project?

The right technology depends on the context. Programming languages, frameworks, databases, and infrastructure should not be chosen because they are new or popular, but because they fit the system’s requirements, the team’s capabilities, and the long-term dependencies they create. Operations, maintainability, and future evolution should also be considered from the start.

INNOQ is vendor-independent and evaluates both existing and new technologies against business requirements, team structures, and strategic goals: Software Architecture and Development

How should software architecture and development work together?

Architecture works best when it is not separated from implementation. Architectural decisions need to prove themselves in real development work and should be revisited as requirements evolve. At the same time, development teams need clear guidance on system boundaries, interfaces, technology choices, and quality goals.

At INNOQ, architecture and development therefore go hand in hand. Our architects are experienced developers themselves and have worked with software throughout different stages of its lifecycle: Software Architecture and Development

How does INNOQ support development teams without creating long-term dependency?

INNOQ can take on different roles depending on the situation: providing individual architects or developers, working alongside existing teams, or taking responsibility for complete teams and applications. Knowledge transfer is part of the engagement. Architectural decisions are documented transparently, and knowledge is shared throughout the project so that teams can continue developing and operating their systems independently.

The explicit goal is to strengthen internal capabilities rather than create long-term dependence on external support: Software Architecture and Development