Ask HN: What's your absolute favorite tech stack, after having tried others?

Over the years, here is the tools that answered all of my needs.<p>Backend:<p><pre><code> - Apollo Server (GraphQL, Javascript&#x2F;Typescript) - Hasura (GraphQL frontend to PostgreSQL, translating GraphQL queries directly to SQL) - Erlang&#x2F;Elixir for distributed applications </code></pre> Frontend:<p><pre><code> - VueJS + VueX + ApolloClient - Bulma (CSS framework, https:&#x2F;&#x2F;bulma.io ) </code></pre> Dev environment:<p><pre><code> - Docker + docker-compose (a single command to spin up the full stack) - Makefile (so easy to write, automate any &quot;long&quot; commands) - KinD (Kubernetes in Docker, https:&#x2F;&#x2F;kind.sigs.k8s.io&#x2F; ) - Lens (a Kubernetes IDE, https:&#x2F;&#x2F;k8slens.dev&#x2F; ) </code></pre> (Pre)Production environment:<p><pre><code> - Managed Kubernetes or k0s ( https:&#x2F;&#x2F;k0sproject.io ) </code></pre> Deployment:<p><pre><code> - Github + PR based workflow - CI pipeline as a multi-stage Dockerfile + Github Actions - CD with ansible + helm + Github Actions</code></pre>

Rails + graphql-ruby + ActiveAdmin + Devise + SideKiq&#x2F;Faktory + Postgres remains a ridiculously productive combination for me.<p>I&#x27;m leaning more towards Faktory these days because it makes it possible to move individual jobs from Ruby to Go if&#x2F;when performance becomes an issue and the much simpler client-side logic makes making performance-related adjustments much simpler and less risky.<p>For the front-end, I&#x27;ve been dabbling with Next.js, and using Tailwind heavily. Deployed to S3&#x2F;CloudFront. I&#x27;m not completely sold on Next.js yet, but I&#x27;ve liked it better than the other options I&#x27;ve tried so far.<p>For deployment of the backend &#x2F; admin tooling, Docker + ECR + EC2 + CoreOS, although I&#x27;m looking at changing out CoreOS for Debian now that it&#x27;s effectively DOA. CI does a Docker image build and pushes to ECR, tagging with the git hash. Deployment consists of changing an environment-specific tag to the desired image, and replacing servers. For blue&#x2F;green deployment you just use 2 different tags (e.g. prod-blue &#x2F; prod-green).<p>I keep a docker-compose config for developers who only work on one piece of the stack at a time and don&#x27;t want to deal with the complexities of managing the local development environment for the rest but don&#x27;t personally use it in development.<p>For context: I&#x27;m a serial technical founder, so time to market is usually the biggest priority for me. Of course, different requirements &#x2F; career paths are often going to lead to other options being more suitable.

React gets used at work and I see it sometimes being a backend dev. For personal projects prefer Vue+TypeScript.<p>Flutter&#x2F;Dart (or perhaps a game engine Unity&#x2F;Godot) for mobile unless there&#x27;s specific support that I need more natively.<p>Actual backend varies depending on the project and can be anything from Go, F#, Kotlin&#x2F;Javalin&#x2F;JDBI, Elixir&#x2F;Phoenix, and an SQL database either PostgreSQL or MySQL, sometimes CockroachDB, or a service like Firebase. TBH, the choice of backend tech doesn&#x27;t actually matter that much once your application has a working foundation. Adding more usually just means replicating whatever, hopefully good patterns you&#x27;ve already created, and each successive addition gets easier as the foundation or examples to copy from get larger. Even a PHP&#x2F;Yii project was as manageable as Ruby&#x2F;Rails if it&#x27;s rolling and cared-for, but I wouldn&#x27;t personally choose these as I prefer static typing and don&#x27;t feel slowed down by it.<p>Don&#x27;t have an answer for Desktop, or need. If I did, I&#x27;d want something direct and cross-platform, maybe Java FX (or now Flutter).

Ruby on Rails.<p>Still have yet to find something else that requires such little configuration and is so complete.

I have developed in many languages and on many tech stacks over the years, but this is my favorite so far:<p>* Linux, Docker, and Ansible (on-prem or cloud; love Linode)<p>* Postgres (I really like SQL Server, too, but it’s not open source)<p>* Redis for caching and other transient data<p>* .NET Core with C# and F#<p><pre><code> Powerful, fast, mature, open source, cross-platform, trustworthy 3rd-party libraries, great documentation and support community — what more could you want? </code></pre> * ASP.NET MVC (WebAPI or Razor views)<p>* jQuery and Tailwind or Bootstrap, but we use Vue, React, and others as necessary<p>* GitLab or GitHub; Jenkins or TeamCity if we need discrete CI&#x2F;CD<p>* Neovim, VS Code, or Rider (for full IDE); ssh, zsh, and tmux<p>=&gt; Very productive and stable tool chain for us going on four years now.<p><pre><code> It’s also *extremely scalable*, both with regard to runtime load and code base organization &amp; maintainability. Lots of other frameworks and languages that are easy to get started with fall apart when the project gets large and complex.</code></pre>

A few years ago I was Go + GraphQL, but in my experience when your schema is too large it&#x27;s hard to scale (in terms of code, not performance).<p>Now I&#x27;m using Rust for the backend (its functional aspects make it a perfect choice for writing business logic) which is not REST (more commands oriented, like create_user, create_post, send_email...) and VueJS for the frontend.<p>Even if it took a little bit of time to learn Rust, I&#x27;m extremely satisfied with the productivity of this stack (Far greater than all the other stacks I&#x27;ve experimented)

Go + plain html + plain js + postgres (or mysql) + nginx. If I need something more fancy, then Vue.

F# on .NET Core is my favorite right now by a fair margin. It runs anywhere, is extremely fast, and jetBrains Rider is great. The .NET ecosystem has a library for everything, and comes with a lot of batteries included. F# is a great compromise between purely functional and pragmatic.<p>If not F#, then Haskell comes in second, and Clojure comes in third.<p>For a web frontend, if it can&#x27;t be server side rendered templates, then React and Typescript.

I built loads of sites. Both small and very large. Primarily with Drupal 7 and Drupal 8. Recently i&#x27;m in the process of building: - <a href="https:&#x2F;&#x2F;hundeavl.dk" rel="nofollow">https:&#x2F;&#x2F;hundeavl.dk</a> - <a href="https:&#x2F;&#x2F;brudensynger.dk" rel="nofollow">https:&#x2F;&#x2F;brudensynger.dk</a> - <a href="https:&#x2F;&#x2F;indspilning.dk" rel="nofollow">https:&#x2F;&#x2F;indspilning.dk</a> - <a href="https:&#x2F;&#x2F;firmaetsynger.dk" rel="nofollow">https:&#x2F;&#x2F;firmaetsynger.dk</a> - <a href="https:&#x2F;&#x2F;konfirmandensynger.dk" rel="nofollow">https:&#x2F;&#x2F;konfirmandensynger.dk</a><p>with ReactJS and a headless CMS with Postgres. I can recommend that stack. Love the NodeJS and JS way more than PHP stuff. For the frontend i&#x27;ve built a custom PostCSS framework thats not bloated.<p>Good luck!

This is what my main focus is on these days<i>:<p>- Vue.js<p>- Tailwind CSS<p>- GraphQL (I haven&#x27;t had a chance to do anything with it yet)<p>- NodeJS (Rust - if I&#x27;m feeling adventurous)<p>- MongoDB (cause it&#x27;s easy to set up)<p></i>I saved up some money and quit my tech job so I can 100% focus on learning these technologies. Right now, I&#x27;m focusing on learning the frontend part of this stack.

Django + PostgreSQL. That&#x27;s it. The frontend is just server-rendered Django templates.

Firebase&#x2F; Fluter.<p>Don&#x27;t care about Vendor lock-in , or how it actually works. It just does<p>Dart is such a pleasure

Backend: Elixir preferably, or Go<p>Transport: GraphQL<p>Frontend: Tailwind, urql, unpoly, Phoenix LiveView, all JS&#x2F;TS frameworks are crap, so still waiting for something decent, but otherwise React.<p>Storage: PostgreSQL<p>Infra: docker&#x2F;k8s, Digital Ocean

Vanilla DOM manipulation on the front-end, template strings and a markdown renderer in Node on the back-end, flat-files for storage until I end up needing SQLite or sometimes NeDB. If something ends up being too slow I break it out and rewrite it in C and ship it as WASM.<p>It isn&#x27;t my favorite aesthetically but as much as I <i>like</i> the various LISPs, Rust and Haskell&#x2F;Purescript I use the above nine times out of ten.

Finding KISS solutions for the project. MVP can also be as a simple as a html and vanilla js to nm validate an idea.

Netlify, Svelte, Hasura. Plus a serverless function here or there if really necessary (but usually not)

Rails API + React<p>Just because after years of being in both ecosystems I am ridiculously productive and don&#x27;t fall into as many traps. With heroku in 30 mins I could have app deployed production ready with auth, CI, API, database setup, and deployment pipeline.

I&#x27;d like to work on a team that uses React on the frontend, Laravel as a thin API backend.<p>But for personal projects (or an early-stage startup), I would drop React and just use plain old Laravel.

Frontend: Vue (typescript)<p>Backend: Go or Java (simple and minimalistic REST-ish API, not a lot of framework stuff), via Docker. AWS Lambda for some things.<p>DB: Postgres (usually managed with AWS RDS)

Used to be a Python backend developer, have used Python, PHP, Javascript and C# on the backend and I&#x27;m now pretty invested in Go. It has its cons but is my favorite experience for backend &#x2F; web services development so far. Environment is easy to setup, compilation is fast, performance is good, language is relatively simple, concurrency feels like a superpower coming from Python and PHP.

Php, mysql&#x2F;postgres for backend, bootstrap for css and vanilla javascript. Sometime I use react for frontend.

Best experiences for me so far have been: Elm on the front talking to Firebase via ports, and Elm on the front talking to a backend via GraphQL.<p>Still a fan of relational databases and SQL. I think Rails apps can get out of hand very quickly, but I actually like much of ActiveRecord.

I don’t have one as I rarely have the same problem twice. For example React is great but for simple problems vanilla JS is just fine and I prefer it to avoid a tool chain for example webpack etc.<p>Back end I’d go with nodejs but if I can get away with a paas maybe I’d use that.

For my content websites: WordPress and Cloudflare.<p>For my apps:<p>- React (tsx)<p>- Fastify<p>- Postgres w&#x2F; Knex<p>- OpenAPI 3.x w&#x2F; TS codegen<p>- Google Cloud (Run &amp; Functions)

Ruby on Rails.

Elixir + Phoenix<p>- Oban for background jobs - Cachex for in-memory caching - Tailwind for styling - Hosted on Gigalixir<p>This stack is the most productive I&#x27;ve ever been

Nothing beats Svelte and Postgres for most web apps these days. Hasura can be a great addition to PG.

The best stack is the one you know. That said, for elegance and productivity it’s python all the way.

tried multiple stacks for last 12 years, for past two years I am enamored with Haskell + Elm

You can QCObjects for front-end and back-end in JavaScript for browsers and NodeJs

react, c#, redis for caching+pubsub, mongo&#x2F;postgres, clickhouse - awesome for analytics&#x2F;mi, algolia for search, mindsdb, logentries for log aggregation, datadog monitoring + catchpoint for synthetic tests<p>killer combo

Backend: Java + Dropwizard + Postgres<p>Frontend: Typescript, no framework

C++ and Typescript. What else do you really need?

Frontend: Svelte Backend: Java Spring

Frontend: HTML<p>Backend: Lib&#x2F;cgi.py<p>Database: Ext4

For those with a lot of web programming experience, I’m also curious what is the easiest stack in which to achieve good security. I’m also interested in hearing about hosting providers - I would particularly want to support smaller companies (rather than big cloud providers) but am not sure how they do with security, DDoS protection, and other such arcane matters.