4 ms·
For the API layer: If you're sure that the app is going to be for the long-term, and you know what you're going to build (rather than a prototype), choose a SOL
by pbowyer 9y ago
For the API layer: If you're sure that the app is going to be for the long-term, and you know what you're going to build (rather than a prototype), choose a SOLID framework.
Having been burned by others, my choice is Symfony. It has set EOL's for each release [1], a strict backwards-compatibility policy [2], is well tested, and has good documentation.
You haven't defined long-term, but I maintain software I wrote over a decade ago, and learned the hard way how important these features are. More than the tech itself.
For everything else: Choose proven technology. Choose databases that aren't reliant on VC funding. Avoid the hype train.
1. https://symfony.com/roadmap#checker https://symfony.com/roadmap#checker
2. http://symfony.com/doc/current/contributing/code/bc.html http://symfony.com/doc/current/contributing/code/bc.html