Ask HN: What stack to migrate

Personally, I’ve found that API/SPA apps end up being more development work per new feature than a single Rails monolith.

Also, anything you switch to is going to feel a lot more productive at first. This is somewhat deceptive, because what your really seeing is that your new software codebase is solving a much smaller problem at first, and of course that's much easier to work with.

You should approach this question with a problem solving mindset. Write down what your main features are and then choose the right tool for the job. Is your app mostly business logic? CRUD updates? Lots of real time push communication? a bunch of custom UI components?

Are customers complaining about the speed of the app? Does it render too slowly or have long wait times? Is it too costly to run? Is development too slow?

Technical decision making is for solving problems, so make sure you know what problem you are solving. Unless you can name a real problem that can't be solved without a new stack, there's no point to rewriting.

For adding features on a monolithic app, you just add features... not sure what kind of answer you're looking for. Rails gives you the ability to build an api on it, you can add react, vue, or any SPA framework on top of it pretty easily.