> Quick rant on just scaling the tech: It's a monolith rails app with a react front end. I chose a boring tech stack because I feel that speed is the most important thing when creating a company. From there, I typically see progressive steps like this:
> 1 Pure vanilla proven web stack of choice (rails, django, laravel). Automate eveything like linting, testing, PR app builds, 99% of devops work.
> 2 Then the front end grows into an SPA as functionality becomes more complex
> 3 More microservices like search emerge into their own thing
This is pretty much the pattern that we've followed for a few companies and has worked great for us. Rails monolith, carving out parts of it to React as they need more interactivity. Has let us iterate quickly with few engineers while still keeping a (relatively) solid base.
> 1 Pure vanilla proven web stack of choice (rails, django, laravel). Automate eveything like linting, testing, PR app builds, 99% of devops work.
> 2 Then the front end grows into an SPA as functionality becomes more complex
> 3 More microservices like search emerge into their own thing
This is pretty much the pattern that we've followed for a few companies and has worked great for us. Rails monolith, carving out parts of it to React as they need more interactivity. Has let us iterate quickly with few engineers while still keeping a (relatively) solid base.