Great question-- and may be worth a detailed/thought out blog post some day! To future proof the service I wanted to use tech that was based on the fundamental

Great question-- and may be worth a detailed/thought out blog post some day! To future proof the service I wanted to use tech that was based on the fundamentals. This boiled down to no special tooling, no special build process, etc. Furthermore I cut out all dependencies I could. I got my third party dependencies down to two (postgres + nginx). Practically speaking this meant: no node, no yarn, no ruby, no webpack, no sidekiq, no redis, etc. The entire service is now Nginx, Postgres and a single binary that has html/css/js/assets embedded inside of it. The entire product is a single Go binary that connects to postgres-- that's it. I could probably do without Nginx, but it has been nice for a variety of reasons and has never given me a headache. My tech/decisions may not be for everyone (that is why I didn't share them initially) but it works incredibly well for me and most products I build.