Ask HN: What would be your stack if you are building an MVP today?

Article summary

The article asks about the preferred tech stack for building a Minimum Viable Product (MVP) today, specifically focusing on the backend. It presents several options, including traditional frameworks like Django and Rails, as well as newer alternatives like Supabase and serverless functions. The goal is to determine the best approach for quickly building and deploying an MVP. The discussion aims to identify the most suitable stack for building an MVP, considering factors like familiarity, scalability, and ease of use.

Main themes

• MVP tech stack
• backend frameworks
• rapid development
• familiarity vs scalability
• Django vs Rails
• serverless options
• local development challenges
• regional talent availability

What commenters say

• Building an MVP with a familiar tech stack is crucial for fast release and iteration.
• The choice of tech stack depends on whether the MVP is for learning a new technology or for creating a product.
• Django is a popular choice for MVPs due to its rapid development capabilities and large community support.
• Using a stack with which one is already familiar is often the fastest way to build an MVP, even if it's not the most trendy or scalable option.
• Supabase and other serverless options can be resource-intensive and may not be the best choice for local development.
• The importance of considering the availability of skills and talent in the local region when choosing a tech stack is emphasized.
• Some argue that Django's built-in features, such as its ORM and admin tooling, make it a more attractive choice than other frameworks like Rails.
• Others suggest that the choice between Django and Rails ultimately comes down to personal preference and the specific needs of the project.