Discussion

Ask HN: Choosing a framework for the next big thing

Let's pretend you're working at a startup to build the next Airbnb. Your team is very small, it's just you and maybe 1-2 other developers. You need to build an application with the following requirements/assumptions:

  - User facing "CRUD"
    - 10+ domain models (eg. House, Guest, Cart, Booking, etc)
    - Lots of forms w/ custom validation
    - Pagination so you can display 1k+ records in tables/infinite-scroll
    - Some areas of rich interactivity (eg. Host availability calendar) but mostly presentational UI / forms
  - Admin panel
  - Background jobs / tasks
    - Scheduled - Run specific job at point in future (eg. Remind user in 3 months about upcoming trip)
    - Recurring - Run cron jobs for repetitive tasks (eg. Run daily report at midnight)
  - Emails / Notifications
    - 10+ custom email templates (booking confirmation, upcoming trip reminder, etc.)
    - Usually sent via background job
  - File uploads / storage (eg. Users upload pictures of house)
  - Auth
    - Users login to book
    - Hosts login to manage their home listings
  - Testing
    - Primarily integration / e2e tests of core flows
You need to choose a framework:

  - Laravel (v9)
  - Rails (v7)
  - Django (v4)
  - Phoenix (v1.6)
Which framework do you choose?

Assume your team knows each framework equally well. Which one allows you to start quickly and still be maintainable 2-3 years down the road while continually adding new features?

2 points ycomverdantnest 4 years ago 4 comments

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton