Ruby on Rails vs Node.js in 2026: Which Backend Is Right for Your Product?

Why the Ruby on Rails vs Node.js Question Still Matters in 2026

The debate around Ruby on Rails vs Node.js remains highly relevant in 2026 because backend technology decisions influence far more than application performance. For founders, CTOs, and product owners, the chosen stack directly impacts time-to-market, development costs, hiring strategy, scalability, maintainability, and long-term business risk.

Many discussions about Rails vs Node.js 2026 focus exclusively on technical benchmarks. In practice, however, products rarely fail because one framework processes requests a few milliseconds faster than another. They fail because teams spend too much time building infrastructure rather than validating business assumptions, or because early architectural decisions create expensive limitations later.

The real question is not whether Ruby on Rails or Node.js is objectively better. The question is which technology delivers the greatest business value for your specific product.

This comparison is based on real-world product development experience across startups, SaaS platforms, enterprise software, healthcare, fintech, logistics, and AI-enabled systems. Rather than focusing on framework tribalism or benchmark wars, it evaluates Rails and Node.js through the lens of business outcomes, scalability, maintainability, and delivery speed.

At the same time, we actively use Node.js, which provides measurable advantages, particularly in real-time communication, event-driven architectures, AI-native products, and specialized microservices.

This comparison focuses on three practical questions: when Rails remains the strongest default choice, where Node.js provides measurable advantages, and when a hybrid architecture delivers the best long-term outcome.

As a Ruby on Rails development company, we regularly help organizations evaluate these tradeoffs before they commit to a new product or modernization initiative:

Ruby on Rails in 2026: Why Ruby on Rails Remains Relevant for Modern Products

Despite recurring predictions of its decline, Ruby on Rails remains one of the most productive and widely used frameworks for building business applications.

The framework continues to evolve through active releases, a mature ecosystem, and a community that remains focused on developer productivity.

While many technologies compete on performance metrics, Rails continues to compete on something equally important: delivering business outcomes faster.

Rails Continues to Evolve in 2026

Ruby on Rails remains an actively maintained framework in 2026, with Rails 8 continuing the platform’s focus on developer productivity, maintainability, performance, and modern application development. Regular releases, security updates, and ongoing investment in technologies like Hotwire demonstrate the framework’s long-term viability.

The growing demand for Rails upgrade and modernization projects is another strong indicator that organizations continue to see strategic value in Rails-based systems.

Rails Still Excels at Product Development

One of Rails’ greatest strengths remains developer velocity.

For startups and growing companies, success often depends on reaching users quickly, validating assumptions, and iterating before competitors.

Rails accelerates product development because many engineering decisions are already standardized. Strong conventions, predictable architecture, mature Gems, and integrated tooling allow teams to spend less time building infrastructure and more time validating product assumptions. For startups and growing companies, this often translates directly into faster releases and lower development costs.

These characteristics significantly reduce the amount of custom engineering required to launch a product.

For SaaS platforms, marketplaces, healthcare applications, B2B products, enterprise portals, and fintech systems, Rails continues to offer one of the fastest paths from idea to production.

Hotwire and Turbo Reduced Frontend Complexity

Another major factor contributing to Rails’ continued relevance is the adoption of Hotwire and Turbo.

Historically, many teams introduced complex frontend architectures simply to achieve modern user experiences.

Today, Rails allows teams to deliver highly interactive interfaces without automatically committing to a large SPA architecture.

By reducing the need for a separate SPA architecture, Hotwire often shortens development cycles, lowers frontend complexity, and reduces long-term maintenance overhead. For many business applications, teams can deliver modern user experiences without expanding frontend staffing requirements.

This does not eliminate the need for React or other frontend frameworks. However, it provides a compelling alternative for organizations prioritizing delivery speed and long-term maintainability.

Rails and AI Integration

One of the defining technology trends of 2026 is AI adoption.

Interestingly, the challenge is rarely building AI features themselves.

The real challenge is integrating AI into existing business systems.

Most organizations already operate software that contains sensitive production data, complex permission models, legacy integrations, compliance requirements, and business-critical workflows. The challenge is rarely the AI capability itself. The challenge is integrating AI into an existing operational environment without disrupting core processes. In this context, Rails often serves effectively as the orchestration layer that connects AI services with user management, reporting, workflow automation, and administrative systems.

Increasingly, organizations are choosing to evolve mature Rails platforms into AI-enabled systems rather than replacing them entirely. In many cases, Rails continues to serve as a stable foundation while AI capabilities are introduced incrementally around existing business workflows.

Our experience suggests that Rails functions extremely well as the backbone of modern AI-powered business software.

Why Companies Continue Choosing Rails with JetRuby

Technology matters.

Experience matters even more.

As stated on our Ruby on Rails services page, “We are recognized experts in Ruby on Rails development.” Over the past 15+ years, JetRuby has helped more than 300 companies worldwide build, modernize, and scale software products.

This experience spans both new product development and large-scale modernization initiatives. For example, JetRuby helped GeneWise Health modernize a 20-year-old healthcare platform by upgrading Ruby on Rails from version 3.2 to 7.x while preserving critical business logic, improving security, and supporting compliance initiatives. JetRuby also built the Ruby on Rails backend for Watchlink, an independent luxury watch trading community, using Ruby on Rails as the foundation for web and mobile applications, real-time messaging, moderation workflows, and role-based permissions.

JetRuby has also supported organizations such as Muttville, where the team helped redesign and scale a nonprofit digital platform, improve content operations, and establish a foundation for future growth. Together, these projects demonstrate a pattern we see repeatedly across industries: Ruby on Rails remains highly effective for both launching new products and evolving mature systems that contain years of accumulated business knowledge.

Our teams have contributed to:

• 225+ delivered projects
• 300+ client engagements
• 45+ million Ruby Gem downloads

This experience extends beyond greenfield product development.

A significant portion of our work involves modernizing existing Rails ecosystems, upgrading legacy applications, reducing technical debt, improving performance, and evolving business-critical systems without disrupting operations.

JetRuby’s expertise has also been recognized within the broader Ruby community.

Ruby creator Yukihiro Matsumoto (Matz) publicly shared JetRuby’s perspective on Ruby on Rails, recognizing the company as an expert in Rails development. For organizations evaluating long-term technology partners, this serves as an additional signal of deep specialization within the Ruby ecosystem.

As software systems become larger, more interconnected, and increasingly AI-enabled, the value of experienced engineering judgment continues to grow.

Rails Upgrade Services Are Growing, Not Shrinking

One of the strongest indicators of Ruby on Rails’ relevance in 2026 is the continued demand for modernization projects.

Many organizations still operate Rails 4, Rails 5, and Rails 6 applications that contain years of accumulated business knowledge.

Legacy Rails systems typically contain years of accumulated business logic, custom Gems, internal frameworks, third-party integrations, and mission-critical workflows. The primary challenge is not rebuilding these capabilities but evolving them safely. Modernization initiatives typically focus on upgrading Ruby and Rails versions, reducing technical debt, improving performance, and gradually evolving architecture without disrupting business operations.

The continued demand for Rails upgrade services is one of the clearest indicators that Rails remains strategically important. Companies continue investing in modernization because replacing business-critical systems often creates more risk than value.

For a deeper look at this topic, see this article. 

Rails Beyond Startups

Rails is still associated with startups by many decision-makers.

That perception is outdated.

Today, Rails powers software across industries ranging from healthcare, insurance, and logistics to SaaS platforms, enterprise software, fintech products, and public-sector systems.

As systems mature, complexity becomes more important than raw development speed.

Organizations accumulate integrations, dependencies, business workflows, compliance requirements, and operational knowledge.

Success in these environments is not about writing code faster.

It is about evolving systems safely.

This is one reason many organizations choose modernization over rebuilding from scratch.

Node.js in 2026: Where Node.js Outperforms Rails

Node.js remains one of the most influential backend technologies in modern software development.

Its popularity is driven by architectural strengths that are particularly valuable in specific application categories.

The key is understanding where those strengths translate into business value.

Event-Driven Architecture and Real-Time Systems

Node.js was built around an event-driven, non-blocking architecture.

Its event-driven architecture makes it particularly effective for real-time communication, streaming workloads, notification systems, WebSocket connections, and messaging platforms that must handle large numbers of concurrent interactions.

Applications such as collaboration tools, chat platforms, streaming systems, and real-time dashboards often benefit significantly from Node.js.

In these scenarios, the architecture naturally aligns with the workload.

TypeScript Strengthens the Ecosystem

One of the biggest developments in recent years has been the widespread adoption of TypeScript.

Today, many organizations treat Node.js as a TypeScript-first backend platform.

TypeScript has significantly strengthened the Node.js ecosystem by improving maintainability, enabling safer refactoring, simplifying onboarding, and creating greater consistency across engineering teams.

This is especially attractive for companies that already maintain large JavaScript and TypeScript frontend teams.

Node.js and AI-Native Products

Node.js has become increasingly common in AI-enabled systems. It is increasingly used in healthcare platforms, fintech products, logistics systems, AI-native applications, and high-throughput event-processing services where asynchronous communication and concurrency are critical.

Its asynchronous architecture is particularly effective for AI API gateways, response streaming, agent communication, event processing, and frontend-facing AI services.

Rather than positioning Node.js as a competing stack to Rails, we typically use it as a specialized tool in which event-driven architecture and high concurrency yield measurable advantages.

In many modern systems, Node.js complements Rails rather than replacing it.

Head-to-Head Comparison: Ruby on Rails vs Node.js in 2026

The question is not whether Rails or Node.js is universally better.

The more useful question is which technology aligns better with your product goals, engineering resources, scalability requirements, and timeline.

The table below summarizes the most important differences from a business and product perspective.

 

Dimension	Ruby on Rails	Node.js
MVP speed	Excellent	Good
Developer productivity	Excellent	Good
Real-time systems	Good	Excellent
AI integration	Excellent orchestration layer	Excellent streaming layer
Scalability	Excellent	Excellent
Hiring pool	Medium	Large
Enterprise modernization	Excellent	Good
Operational complexity	Lower	Higher
Long-term maintainability	Excellent	Depends on architecture
Best fit	SaaS, marketplaces, B2B	Realtime, streaming, event-driven

Performance: Looking Beyond Benchmarks

The discussion around Node.js vs Rails performance often focuses on raw benchmarks.

In practice, most startups and enterprise products are limited by architecture, database design, infrastructure choices, or business complexity long before framework performance becomes the bottleneck.

Our view based on real-world projects is straightforward:

Rails delivers more than enough performance for the vast majority of SaaS products, marketplaces, healthcare platforms, fintech applications, internal business systems, and enterprise software.

Node.js demonstrates its strongest advantage when workloads involve persistent connections, event streams, WebSockets, notifications, real-time updates, and other highly concurrent I/O operations.

For most organizations, development speed and maintainability have a greater impact on business outcomes than differences in benchmark-level performance.

Scalability: Both Technologies Scale

A common misconception is that Rails struggles with scale while Node.js scales effortlessly.

Reality is more nuanced.

Rails applications commonly scale through a combination of horizontal scaling, background processing, caching, CDN integration, and database optimization. Many large enterprise systems continue operating successfully on Rails because the underlying architecture was designed correctly from the beginning.

Node.js excels in environments where event-driven patterns dominate system behavior.

This makes it especially attractive for:

• Notification systems
• Communication platforms
• Streaming applications
• Event-processing services

In most cases, scalability is an architectural challenge rather than a framework limitation.

Developer Productivity Often Determines Product Success

One of Rails’ biggest advantages remains developer productivity.

Rails was specifically designed to reduce repetitive engineering work through conventions and proven patterns.

Rails reduces repetitive engineering work through conventions and established patterns. As a result, teams typically benefit from faster onboarding, less boilerplate code, a more predictable architecture, and shorter feature delivery cycles.

Node.js offers greater flexibility.

That flexibility can be an advantage for experienced teams, but it also introduces additional decisions around architecture, frameworks, validation, security, and project structure.

For startups, fewer decisions often translates directly into faster execution.

Cost and Total Cost of Ownership

Technology decisions should always be evaluated through the lens of total cost of ownership (TCO).

Rails often provides a lower total cost of ownership during the early stages of product development. Its convention-driven approach, mature ecosystem, and extensive library support enable teams to deliver features faster with fewer engineering resources. As a result, organizations can launch MVPs sooner, reduce implementation complexity, and focus investment on product validation rather than infrastructure and framework-level decisions.

Node.js can provide greater flexibility as systems grow.

However, that flexibility often comes with additional architectural decisions that teams must make themselves.

For founders evaluating Node.js vs Rails developer cost, the important metric is not hourly rates.

The important metric is how quickly the product reaches the market and starts generating feedback, users, and revenue.

Which Backend Is Right for Your Startup in 2026?

Which is Better for a Startup: Rails or Node.js?

The answer depends less on technology and more on business goals.

Many founders approach the decision as if they must predict the perfect architecture for the next ten years. In reality, the goal is usually much simpler:

Build the right product, validate demand, and maintain flexibility as the business evolves.

If your primary objective is rapid product validation, Rails is often the strongest default choice.

If your product fundamentally depends on real-time communication or high-frequency event processing, Node.js may deserve greater consideration.

A useful framework looks like this:

Choose Rails if:

• You are building a marketplace
• You are launching a SaaS platform
• You are building a B2B application
• You need an MVP quickly
• Business workflows are more important than real-time communication
• You want lower initial development costs

Consider Node.js if:

• Real-time communication is the core product
• You are building a low-latency event-processing platform
• Your workload depends on thousands of concurrent connections
• Streaming is a primary business requirement

Consider a Hybrid Architecture if:

• You need rapid product development today
• Real-time requirements may emerge later
• You want flexibility without premature complexity

For founders evaluating technology choices, we also recommend reading this article.

Scenario A: Marketplace MVP Delivered in Eight Weeks

Consider an early-stage marketplace startup.

Consider an early-stage marketplace startup preparing to launch its first version of the product. The founders had a clear vision but limited resources, making speed of execution more important than architectural sophistication. Their immediate goal was not to optimize for hypothetical future scale, but to validate demand, understand customer behavior, and reach product-market fit as quickly as possible.

After evaluating several backend options, the team selected Ruby on Rails because it offered the shortest path from idea to production. Rails conventions, mature Gems, and integrated tooling allowed developers to focus on business functionality rather than infrastructure and framework-level decisions. As a result, the MVP reached production in approximately eight weeks.

More importantly, the company was able to start collecting customer feedback, testing unit economics, and validating core assumptions before committing to larger engineering investments. This illustrates one of Rails’ enduring advantages: it allows startups to optimize for learning speed and business validation rather than premature architectural optimization.

Can You Start with Rails and Add Node.js Later?

One of the most common concerns among founders and product owners is whether choosing Rails today limits flexibility tomorrow.

In most cases, the answer is no. Modern software systems evolve continuously. The architecture that makes sense for an MVP is rarely identical to the architecture supporting millions of users years later.

A common and highly effective pattern is:

1. Launch with Rails.
2. Validate the business model.
3. Scale the product.
4. Extract specialized services only when justified by real requirements.

This approach avoids premature complexity while preserving future flexibility.

Instead of guessing which technologies might become necessary someday, teams can make decisions based on actual usage patterns and business needs. This is where hybrid architectures become particularly valuable.

When to Use Both: Microservices and Hybrid Architectures

One of the biggest misconceptions in software architecture is that organizations must commit to a single backend technology for the entire lifetime of a product.

In reality, successful products evolve.

The architecture that makes sense for an MVP is not necessarily the architecture that will be optimal three years later. Likewise, introducing unnecessary complexity too early can slow down development, increase costs, and delay product validation.

This is why many modern systems are no longer built around a strict Ruby on Rails vs Node.js decision. Instead, they use both technologies, where each creates the greatest value.

Why Hybrid Architectures Are Becoming the Norm

As software grows, different parts of the platform begin serving different purposes.

As platforms mature, different parts of the system begin serving different purposes. Core business workflows require stability and maintainability, while notification services, AI interactions, and customer-facing real-time features often demand different architectural characteristics. This is where hybrid Rails + Node.js architectures become attractive.

Optimizing every component with a single technology stack is possible, but it is not always the most efficient approach.

Hybrid architectures allow engineering teams to keep Rails where Rails is strongest while introducing Node.js only where its architecture delivers measurable benefits.

In our experience, this often creates the best balance between:

• Development speed
• Maintainability
• Scalability
• Operational efficiency
• Long-term flexibility

The discussion increasingly shifts from Ruby on Rails or Node.js to Ruby on Rails and Node.js.

Scenario B: A Dedicated Node.js Notification Service Inside a Rails Product

Consider a mature Rails platform serving a rapidly growing customer base. As the product evolved, users began expecting real-time capabilities such as instant notifications, live activity updates, and streaming interactions. While these features introduced new technical requirements, the core application continued to perform well and remained responsible for business-critical functions including user management, billing, permissions, reporting, and administrative workflows.

Rather than rebuilding the entire platform around a new technology stack, the engineering team adopted a more targeted approach. Rails remained the system of record and continued handling core business logic, while a dedicated Node.js service was introduced to manage real-time communication and event delivery. The two systems communicated through APIs and asynchronous messaging, allowing each technology to focus on the workloads it handled most effectively.

This architecture enabled the company to scale real-time features independently without disrupting existing operations or increasing complexity across the entire platform. Most importantly, the organization avoided the cost, risk, and delivery delays associated with a large-scale rewrite. The result was a system that combined Rails’ strengths in business workflows and maintainability with Node.js’s advantages in event-driven, high-concurrency workloads.

This pattern has become increasingly common in modern software organizations. In many cases, Node.js creates the most value not by replacing Rails, but by complementing it as part of a carefully designed hybrid architecture.

AI-Driven Enterprise Modernization in Insurance

One of the most significant technology trends of 2026 is the use of AI to modernize existing enterprise systems rather than replace them entirely.

For many organizations, the challenge is not building new software. It is evolving complex platforms that contain years of accumulated business logic, integrations, compliance requirements, and operational knowledge. In these environments, maintaining system stability is often more important than introducing entirely new technologies.

During a modernization initiative for Trustmark, JetRuby applied an AI-assisted approach to help transform a complex insurance ecosystem while preserving critical business workflows and reducing migration risk. Rather than relying on a large-scale rewrite, the project focused on understanding existing systems, documenting dependencies, and incrementally modernizing the platform.

Over the course of the engagement, more than 40 enterprise applications were upgraded, migrated, or modernized while maintaining business continuity. The project demonstrated that AI can accelerate modernization efforts when combined with experienced engineering oversight and a deep understanding of existing systems.

This trend is also relevant to the Ruby on Rails vs Node.js discussion. In mature organizations, the question is often not which framework to replace everything with. The question is how to evolve existing systems safely while introducing new capabilities such as AI, automation, real-time services, or specialized microservices. In many cases, Rails continues to serve as the core business platform, while complementary technologies, including Node.js, are introduced where they offer specific advantages.

Common Mistakes When Choosing Between Rails and Node.js

Choosing between Ruby on Rails and Node.js is rarely a purely technical decision. In practice, many costly architecture mistakes happen when teams optimize for hypothetical future requirements instead of current business needs. Across startups, scaleups, and enterprise organizations, several patterns appear repeatedly.

Optimizing for Scale Before Product-Market Fit

One of the most common mistakes is selecting a technology stack based on traffic volumes the product may never reach. Early-stage companies often worry about supporting millions of users before they have validated demand. In reality, delivery speed, customer feedback, and rapid iteration usually create more business value than theoretical scalability advantages. For most startups, the ability to launch and learn quickly is far more important than optimizing for infrastructure challenges that may be years away.

Choosing Based on Benchmarks Instead of Business Requirements

Benchmark comparisons often dominate technology discussions, but they rarely reflect real-world product development. Database design, application architecture, integrations, security requirements, compliance constraints, and engineering execution typically have a greater impact on system performance than the choice between Rails and Node.js. The most successful technology decisions are driven by business requirements rather than benchmark results.

Overestimating Future Traffic and System Complexity

Teams frequently design systems for a future state that does not yet exist. This can lead to unnecessary infrastructure, longer development cycles, higher operational costs, and increased architectural complexity. Successful products typically evolve their architecture in response to actual growth rather than speculative forecasts. Building for today’s requirements while preserving flexibility for tomorrow is often the more effective strategy.

Introducing Microservices Too Early

Microservices can provide significant benefits at scale, but they also introduce operational overhead, deployment complexity, distributed system challenges, and additional maintenance requirements. Many products adopt microservices long before they have a genuine need for them. In many cases, a well-structured Rails monolith provides a faster, simpler, and more maintainable path to growth, while specialized services can be extracted later as business requirements become clearer.

Ultimately, the best technology decisions are not driven by framework popularity or industry trends. They are driven by a clear understanding of business goals, delivery timelines, operational constraints, and expected growth patterns. Whether you choose Rails, Node.js, or a hybrid architecture, aligning technology decisions with product strategy is usually a stronger predictor of success than any individual framework feature.

FAQ

Is Ruby on Rails faster than Node.js?

The answer depends on the workload.

For typical SaaS platforms, marketplaces, healthcare applications, and business systems, Rails delivers more than enough performance when supported by good architecture, caching, background jobs, and database optimization.

Node.js generally performs better in I/O-bound workloads involving WebSockets, notifications, event streaming, and large numbers of concurrent connections.

For most organizations, development speed, maintainability, and reliability create more business value than differences in benchmark-level performance.

Which is better for a startup: Rails or Node.js?

For most startups, Rails remains the stronger default choice because it enables faster product validation and lower initial development costs.

As illustrated in Scenario A, an MVP can often reach production in approximately eight weeks using Rails conventions, mature Gems, and established development patterns.

Node.js becomes more attractive when real-time communication, event streaming, or high-frequency event processing are core product requirements.

The best choice should be driven by business goals rather than technology trends.

Can Ruby on Rails scale like Node.js?

Yes.

Rails scales through the same techniques used by most modern web platforms, including horizontal scaling, background processing, caching, and database optimization.

Enterprise organizations continue operating large-scale Rails systems across healthcare, logistics, insurance, SaaS, and financial services.

Node.js naturally fits event-driven architectures and microservices, but scalability is ultimately an architectural challenge rather than a framework limitation.

Is Ruby on Rails still relevant in 2026?

Absolutely.

The continued demand for Rails upgrades, Ruby upgrades, dependency modernization, and AI enablement initiatives demonstrates that organizations continue investing heavily in Rails-based systems.

Companies do not modernize platforms they consider obsolete. Instead, they modernize technologies that continue delivering business value.

For a deeper discussion, see our analysis of why Ruby on Rails is still widely used for modern application development.

What companies use Ruby on Rails vs Node.js?

Ruby on Rails remains widely used across SaaS, healthcare, fintech, logistics, insurance, enterprise software, and public-sector applications.

At JetRuby, many engagements involve building, scaling, modernizing, and extending mission-critical Rails platforms operating in complex and regulated environments.

Node.js is frequently selected for real-time communication systems, AI-native products, streaming services, healthcare applications, fintech platforms, logistics systems, and event-driven architectures where high concurrency is a core requirement.

Final Thoughts: Ruby on Rails vs Node.js in 2026

The debate around Ruby on Rails vs Node.js often becomes unnecessarily polarized. In practice, successful products are rarely built by following technology trends.

They are built by selecting technologies that support business goals, accelerate delivery, simplify operations, and create long-term flexibility.

Our view, based on more than 15 years of experience building and modernizing software systems, is straightforward.

For most startups, SaaS products, marketplaces, B2B platforms, enterprise applications, healthcare systems, fintech products, and AI-enabled business software, Ruby on Rails remains one of the strongest default backend choices available in 2026.

Its combination of development speed, mature architecture patterns, maintainability, and business-focused productivity continues to provide a meaningful competitive advantage.

Node.js is not a replacement for Rails. It is a powerful complementary technology that excels in real-time communication, event-driven architectures, streaming workloads, AI interaction layers, and specialized microservices.

Increasingly, the best answer is not choosing one or the other. It is understanding when to use Rails, when to use Node.js, and how to combine both effectively.

Whether you are launching a new product, modernizing a legacy platform, introducing AI capabilities, or evaluating a migration strategy, the most important decision is not selecting a framework.

It is selecting an architecture and engineering partner capable of supporting your business for years to come.

Schedule a Consultation

If you are evaluating Ruby on Rails, Node.js, or a hybrid architecture for your next product, we can help you make the decision based on business requirements, scalability goals, technical constraints, and long-term maintainability.

If you are evaluating Ruby on Rails for a new product or modernization initiative, you can talk to our Ruby on Rails experts to get a structured assessment of architecture, timeline, and team setup. Ruby on Rails development consulting.

If you have already decided to build with Rails and want to accelerate delivery, you can start faster by hiring a dedicated Ruby on Rails development team integrated into your product roadmap. Hire Ruby on Rails developers.

If you are still comparing options beyond Rails and Node.js, our guide on how to select the right tech stack provides a broader framework for evaluating technologies based on business goals, scalability requirements, and product strategy.