Ask HN: What tech stack would you choose for a serious, long-term business app
As we&#x27;re talking business and long lifetime...<p>First point: nothing Microsoft. Done that show for 20 years and been through all the marketoid schizophrenia promoted rewrites for no business value. Now the new &quot;start again&quot; is .Net core and a big chunk of stuff just isn&#x27;t portable and never will be. Plus the price gouging, licensing hell etc when you have to scale up. Entire ecosystem is a wasteland of unmaintained crap and automation prospects are terrible. Forget it at this point. I&#x27;m done.<p>At this point, I&#x27;d pick Java + Spring + Postgres + CentOS. Does most of the stuff you need out of the box, good support available, long product lifespan, well maintained, possible to automate everything. No SPA, just old fashioned dynamic pages with light weight in house JS framework that does partial page replacement, simple validation etc via DOM. Not even jQuery which has been nothing but hell to upgrade so I&#x27;m loathed to pick anything more complicated.<p>PaaS: none. Either in house or old fashioned colo, with HP hardware. If you have to go PaaS, then AWS which seems the most glacial in deprecation so far.<p>Edit: also desperately avoid any non portable abstractions and vendor specific features. They will ruin you. For example when someone suggests a database engine, hide it behind hibernate and only use the hibernate API!<p>Edit 2: it is important to assign an exit cost for every decision as well. What&#x27;s true now is not going to be in a decade.