DEV Community

What would your tech stack of choice be for a new web dev project?

Ben Halpern on February 09, 2022

Let's say you are hired to create a web app for a company that describes itself as "Etsy for dogs" (whatever that means). You'll be the only devel...

Read full post

Brian Heidrich • Feb 10 '22

Frontend: Svelte + Tailwind
Backend/Auth: NHost (Hasura/Postgres)

Giorgi Kharshiladze • Feb 9 '22

TailwindCSS + Next JS (with Typescript) + Prisma (with Postresql) - very simple setup, easy to deploy, nice dev experience. You could go with custom node js server alongside with nextjs if you want to, but for the most small/mid size projects NextJS builtin API routes feature should be good enough.

Mike Dabydeen • Feb 12 '22

I have been using the same with Supabase (PostgreSQL). Easiest stack to work with and reason about

Chris Ochsenreither • Feb 9 '22

Database: DynamoDB
API: AWS Gateway API w/ Lambdas (any language)
Auth: AWS IAM
Frontend: NextJS on Vercel
CSS: Ask my web designer

All of this will scale automatically, requires no dedicated servers and is served from edge locations.

DevFranPR • Feb 10 '22

Love the "Ask my web designer" part :')

menottiRicardo • Feb 13 '22

Can you give a little more detail on the Api? I've wanted to try that combo but I'm not sure about the cold start

Chris Ochsenreither • Feb 16 '22 • Edited

Cold starts can be long for interpreted languages like Python, Node.js and Ruby. Here's a comparison of 20 lambda executions from cold start where a user is created:

Create User

Payload:

{
    "email_address": "jonathon.doe@hotmail.com",
    "first_name": "Jonathon",
    "last_name": "Doe",
    "password": "vaFR6z2D8xstaao4EyvP"
}

Metric	Duration (ms)	Duration (ms)	Memory Used (MB)	Memory Used (MB)
Trial	Node.js 14.x	Python 3.7	Node.js 14.x	Python 3.7
1	753	203	80	69
2	408	17	82	69
3	9	35	82	69
4	39	30	82	69
5	22	34	82	69
6	18	28	82	60
7	21	36	82	69
8	8	35	82	69
9	28	43	82	69
10	10	31	82	70
11	9	21	82	70
12	7	38	82	70
13	23	36	82	70
14	8	33	82	70
15	8	21	82	70
16	17	43	82	70
17	22	27	82	70
18	22	43	82	70
19	8	68	82	70
20	8	12	82	70
Sum	148	834	1638	1391
Average	72.4	41.7	81.9	70
Median	17.5	34.5	82	70

menottiRicardo • Feb 16 '22

thanks a lot for that info, are you using Express or Nest for Nodejs?

Chris Ochsenreither • Feb 16 '22 • Edited

I'm not using a framework for these functions. API Gateway provides the url REST endpoints and those endpoints are linked to event handler functions. The functions are stand-alone and just import the packages required within the function.

Bobby Iliev • Feb 9 '22

The TALL stack 🙌

Tony Lea • Feb 9 '22

I second that! It's essentially the Rails/Hotwire version for PHP, Larave/Livewire. In fact Livewire was created before Hotwire.

The TALL stack makes building reactive apps so simple and fun 😊

peerreynders • Feb 9 '22 • Edited

FYI: PETAL Stack in Elixir

First, the base foundation of Elixir + Phoenix + LiveView is powerful. It has been the inspiration for other projects like Laravel LiveWire and Rails Hotwire.

Caleb Porzio

@calebporzio

Got inspired by Phoenix LiveView, decided to hack on a prototype for Laravel, and holy crap. I feel like this is the kind of thing that will change the game for me.

Will post a demo soon

03:21 AM - 16 Jan 2019

2018-09-07

Rails Hotwire was introduced 2020-06-24 as NEW MAGIC.

Meanwhile tallstack.dev was public 4 months before PETAL.

Sometimes chain reactions are just inevitable.

Ben Halpern • Feb 9 '22

TL;DR?

Bobby Iliev • Feb 9 '22

Tailwind, Alpine.js, Laravel, and Livewire. A full-stack development solution, built by Laravel community members.

Posandu • Feb 10 '22

Yay finally PHP is becoming a thing

DevFranPR • Feb 9 '22

Wow I didn't know this was a thing. Now I'm interested.

Dĵ ΝιΓΞΗΛψΚ • Feb 11 '22

I wouldn't dream of doing it any other way than following:
Frontend: Svelte
Css: Tailwind
REST Api: FastEndpoints (.Net 6)
Data Access: MongoDB.Entities
Architecture: Vertical Slices with REPR pattern for endpoints.

Warren Buckley • Mar 3 '22 • Edited

Huh, I had never heard of Fast Endpoints until recently (Nick Chapsas did a video about it). Need to write a little toy project to try it out.

Watermelol • Feb 10 '22

Frontend: Vuejs + Tailwind
Backend: Django with Restful Framework, MySQL

Daniel Albuschat • Feb 9 '22

Definitely FastAPI (Python) backend and Svelte with TypeScript frontend. Blazingly fast. ⚡

Put in PostgreSQL as the DB, which can be SQL, MongoDB and Redis at the same time. It's just so overpowered. 💪

Ivan Jeremic • Feb 10 '22

I'm confused, how is it mongo.

Daniel Albuschat • Feb 10 '22 • Edited

Very good question 😊
Postgres has native JSON support and allows you to access json fields (even unlimited nested ones) in SQL statements. This gives you the schemaless flexibility of MongoDB if you for example build a simple table with "key varchar" and "data json" fields. But at the same time you can build very complex queries, write DB-procedures, triggers and all the other goodies of powerful RDBMs.

webbureaucrat • Feb 10 '22

It's not a perfect analogy, but Postgres is object-relational. You can have columns that are typed as objects instead of just regular built-in types, so you can get some of the benefits of object storage without fully committing to the document db model.

Isaac Lyman • Feb 10 '22 • Edited

My go-to is Vue 3 + Typescript + SCSS on the front end, Node + Express + Postgres on the back end, and Heroku. I can have a webapp up and running in no time at all with this stack. For me it's all about familiarity and speed-to-value. If you're more comfortable with something else, use that.

Sherry Day • Feb 9 '22

Tempted to go with Rails/Hotwire. Seems sort of tough to sprinkle in, but if I get to start from scratch I feel like I could be productive committing to that approach.

Diner Das • Feb 9 '22

I feel similarly.

Jesse Warden • Feb 10 '22 • Edited

The REGAL stack: ReScript Elm GraphQL Amplify & AppSync, Lambda

UI: Elm + TailwindCSS + Amplify to host + AWS CodeDeploy wired up to repo
API: ReScript + GraphQL + AppSync to host + Lambda to satisfy GraphQL calls

Hung Vu • Feb 10 '22

It really depends on what the requirements are. My one-choice-fit-many solution is:

Front end: React - TS, Material UI
Back end: NestJS - TS, with TypeORM
Database: PostgreSQL

Going for an exotic solution will be hard to maintain in the long term (hiring talents, etc.)

For cloud deployment, Google Cloud. As Google Workspace is widely used by organizations, even small one, it will be easier to integrate.

Front end + Back end: App Engine or Compute Engine
Database: Cloud SQL
SSO Auth: Google Cloud Identity (essentially Firebase, but with more compliances)
Infrastructure as Code: Terraform

I'm actually writing about the stack above if anyone is interested in. hungvu.tech

Bruno Prieto • Feb 9 '22

Rails + Hotwire

Benny Powers 🇮🇱🇨🇦 • Feb 10 '22

If the front end isn't based on web components, your just setting yourself up for trouble

Ilya Shaplyko • Feb 12 '22

Why?

Benny Powers 🇮🇱🇨🇦 • Feb 13 '22

Loading performance
Vendor lock in
Future proofing
Incremental adoption
Developer experience

Asad Ullah • Feb 16 '22 • Edited

Quite an open ended question without telling:

Budget
Estimated Traffic for the system
Product Timelines (time to market etc.)

Tech stack primarily depends on these metrics and when the choice is made without considering these, the end result is:

Personal preferences causing increased tech debt
Performance issues when system scales
If the product is a hit, a mess for the engineers who will be on board in future to deal with technical debt.

Nicholas Stimpson • Feb 9 '22

Vanilla HTML, Vanilla JS, Vanilla CSS for the frontend. Spring Framework for the backend.

Philipp • Feb 14 '22

Finally someone who ditches all the frontend frameworks! The web platform is already powerful enough.

Max Fahl • Feb 14 '22

But there's also a reason for why people go with Sass, Typescript and front-end libraries/frameworks. For me it depends on the size of the project. I really enjoy vanilla JS (es6) when I feel like the complexity doesn't require a framework.

Matteo • Feb 10 '22

Depends on the requirements

guledali • Feb 10 '22 • Edited

Good answer, requirements first and secondly always choose the easiest path and less reinventing the wheel.

For example rather than building your own ecommerce framework and application just use the shopify template and ready-to-use solutions. Focus on actually solving the problem and delivering to your customers is the key.

David Woodward • Feb 10 '22 • Edited

Node.js, Fastify, Typescript, Prisma & Postgres, server rendered html templates instead of a frontend framework, TailwindCSS, Stripe for payments, Auth0 for authentication, Mixpanel for analyitics. All deployed to Heroku for $0 unless I want a custom domain name, in which case the price jumps to $7 plus whatever it costs to buy the domain from Google.

If anyone else is interested feel free to fork this starter github.com/dwoodwardgb/node-monoli...

By the way I'm not anti frontend, I've spent years on it professionally, I just think it's unnecessary for most MVP's

Alain D'Ettorre • Feb 10 '22

Firebase + any frontend framework is unbeatable for speed and simplicity for me. It also comes with no initial costs. Then, if the project takes off, switch to anything else, if not kill it with fire.

If the project has any specificity (constraints, needs) I pivot around that

Hotdogerino • Feb 16 '22

Why kill it?

Posandu • Feb 10 '22

React for Frontend
PHP for backend
Material UI / Tailwind as the UI component library
MySql/Postgre for Databases

Ilya Shaplyko • Feb 12 '22

Any react tailwind UI libraries you would suggest?

Clavin June • Feb 10 '22 • Edited

Svelte + Golang + Supabase

Niels Swimburger.NET 🍔 • Feb 9 '22 • Edited

TypeScript and SASS for frontend without frameworks, ASP.NET Core for backend, PostgreSQL for database, Azure App Service for Linux for hosting

Marcos Maia • Feb 9 '22 • Edited

KISS - NestJS(Typescript) + Postgres.

Front end I would risk betting on Flutter as it's developing really fast as a good alternative to minimize codebase and promote reuse for Web, Desktop and mobile clients.

Jan Peterka • Feb 10 '22 • Edited

I sadly have only one stack in my sleeve currently:
MySQL + Flask (with Turbo) + Bootstrap (+ Stimulus.js - no need for bigger FE in this case I guess)

But I would like to look into:

PostgreSQL instead of MySQL
Tailwind instead of Bootstrap
Django instead of Flask (if I'd be able to use Turbo, I'm addicted to it 😅)
Rails instead of Flask (but I have only little XP in ruby/Rails, so it would take a lot longer to create this.

Also, if it's "for dogs", maybe it should be w3 dapp based on DogeCoin? 🐶

mirko • Feb 10 '22

Go + Postgresql + Vue3

Vincent A. Cicirello • Feb 10 '22

If you were building "Etsy for dogs", then in addition to all of the great suggestions in the comments, you'd also need a room full of puppies as beta testers, and probably a bucket of dog treats as incentives.

guledali • Feb 10 '22 • Edited

A good starting point would be Redwood.JS for me, if I was building for a company now.

Well documented framework, solid structure both frontend & backend
Growing community, serveral channels discord and so forth.
It's following the current trend which is SPA + JSON but it does this togeher and in a opnionted omakase style that's suitable for teams and solo dev.
Not really related to redwood.js but it's good to bring up.
Easy to find javascript developers in general, what's so unique about javascript is that you can always expect someone to know it, the might not be good at it or like it very much. Hate or Not but javascript is the lingua franca of ~~Development~~ Programming in General.

Using a web framework is always going to help you reaching your goal faster, for example there are different way of travelling to reach your place. You could for example use a bike, car or airplane. I would always recommend travelling the most comfortable way. The developing a product is a never reaching destination, so taking an airplane is going get you further than a bike and it's surely going to be more comfortable too.

A web framework is exactly like that.

guledali • Feb 12 '22 • Edited

I would actually recommend for teams out there. Before settling on any technologies, to do an actual 1-4 months of case studies before adopting anything!

Really ask yourself

If the codebase is maintaible in such early-stage?
Does the framework of use prodivde much?
Are our devleopers able to iterate fast enough and deliver features?

Matt Ellen-Tsivintzeli • Feb 10 '22 • Edited

Some flavour of Linux, Django, postgres, vanilla javascript and css.

If APIs are necessary then there's an addon for Django that does it.

Javel Rowe • Feb 10 '22

HTML, JS, Tailwind + Node.js, MongoDB

John Peters • Feb 11 '22

Follow Stackoverflow: ASP.NET using .Net 6.0.

Checkout a Blazor front-end which is WASM capable.

Or Pick any front-end desired, with React leading the way.

Host it on Azure

tamusjroyce • Feb 25 '22

html + sass. No scripting. Full page post backs using scalable endpoints built in rust. I might throw Deno in the mix as a dev tool & writing quick internal dev & CI scripts.

Then I would append partial postbacks when the browser supports it.

Tyler Smith • Feb 10 '22

If I have to live on it forever? Tailwind, Alpine.js, Laravel & Livewire (colloquially known as the TALL stack). I've used tons of frameworks, but Laravel's first-party ecosystem seems like the safest bet.

I feel like picking React frameworks like Next or Remix would mean having to rewrite the whole front-end every couple of years to keep up with JavaScript churn.

Bernd Wechner • Feb 10 '22

I use LLUPP - and if you never heard of that it's because I made it up, but it's a thing and if it ever takes off, I was there first ;-)

it's a direct derivation of the LAMP acronym (Linux, Apache, MySQL, PHP), but uses better tech (Linux, Lighttpd, Uwsgi, Python, Postgresql) ...

But each to their own. You'll use what you use. LLUPP makes no mention, as LAMP doesn't of the front end part of the stack. And well there I've used plain of JavaScript, a bit JQuery but otherwise, I like light front ends and keep front end work to the minimum I guess. Again each to their own, and their context. Much of this is defined ultimately by context ...

Syed Faraaz Ahmad • Feb 11 '22

Ruby on Rails. Easily. The speed at which you can prototype/scaffold/build things with rails remains unparalleled

Adam Crockett 🌀 • Feb 9 '22

GraalVM Kotlin Quarkus with SvelteKit

Cajaye Clarke • Feb 10 '22 • Edited

Svelte (vite)
SCSS
Node/Express
Typescript
Prisma
Planetscale

Bruno Paz • Feb 20 '22 • Edited

I would need to understand better all the requirements first (like performance and scalability requirements for example, to give a more informed decision. ;)

Still, as starter point, for a medium sized web application I would be interested in using Nuxt3/SvelteKit (withTypescript), Tailwind for styles, Prisma and Postgres for database.

I believe all this Next/Nuxt/SvelteKit with SSR will be the rebirth of the more monolith / single deployment applications, similar to what we would build in the 2000s using PHP, Django or Rails, but with a much more enjoyable architecture and development experience on the frontend, due to the tooling evolution and component based architecture, as well as Typescript.

If the business logic would be very heavy and complex, then I would probably separate the API and build it in Go, while keeping the same stack for the frontend

jonosellier • Feb 19 '22 • Edited

Frontend: Angular
Backend: NestJS
DB: Postgres (with Prisma)

Why? Both have excellent tooling and have similar structure in terms of separation of concerns. I also think their opinionated nature is selling point. It's better that I have things be done one very good way than my favorite way. It makes it easier to onboard new people to the codebase if certain baseline standards are easily accessible through the docs. Postgres with Prisma gives me nice type safety and lets me abstract away simple queries with the power to do raw SQL for optimization down the line.

Etienne Burdet • Feb 10 '22 • Edited

I'm trying SvelteKit over Supabase and it seems super promising. I could get fancy by replacing SvelteKit with Solid and Astro or Slinkity, but Svelte is really solid right now and I've reach a state of good productivity with it.

I wish I had an opportunity to launch a fullstack project on Phoenix, but I'm afraid it won't come…

Zoltán Szőgyényi • Feb 9 '22

Tailwind CSS + Flowbite + Laravel + MySQL.

ΣRD βΩISΩΠ • Feb 15 '22

What's flowbite for Sir ?

Zoltán Szőgyényi • Feb 15 '22

Components on top of Tailwind CSS.

ΣRD βΩISΩΠ • Feb 15 '22

Thanks

buphmin • Feb 15 '22

This is a tricky one as it depends on the product which stack makes the most sense. Ecommerce is tricky because how accustomed we have gotten to high quality sites, such as Amazon, which load incredibly fast (most of the time). In my experience people are extremely picky with performance when they are purchasing things.

I'm going to assume there isn't an Ecommerce framework that exists and it needs to be built from scratch.

So given that I'd probably consider:

Testing:

cypress
language specific unit test frameworks

Backend:

Typescript NestJS (fastify adapter)
Golang for performance critical components if needed
Postgres
Deploy to AWS since I'm familiar with it with ECS
Consider cache for mostly static parts

Frontend:

VueJS typescript, it's the fastest/cleanest way to develop FE I've found so far.
CSS depends on the design, find the closest or most flexible framework to do what I need

Scott Barrow • Feb 15 '22 • Edited

The question often gets interpreted as "what's your favourite tech stack to work in"...hence the knee-jerk "ALLTHETHINGS" answers below without really considering the requirements given.
I'd love to see a solo dev implement a stack that requires an acronym, one of which being Typescript

It would need to be a well informed decision based on budget, resources, product market, product longevity.
Given the little information provided -
I would start with a Rails + Hotwire + Tailwind stack for MVP/product market fit and potentially consider a client side framework once it outgrows it's use, which may be a long time.
Put the horse before the cart

Marc Scholten • Feb 14 '22

For SPAs: IHP Backend (ihpbackend.digitallyinduced.com/) for the Backend and React + TypeScript for the Frontend.

For more simple CRUD apps: IHP for frontend and backend (ihp.digitallyinduced.com/)

donny roufs • Feb 10 '22

.net core with react(tsx) and chakra-ui.

webbureaucrat • Feb 10 '22

Postgres
PostgREST
Haskell
Elm
ReScript

Easy refactoring and no runtime exceptions.

Quooston • Feb 12 '22

SQL Azure backend
C# domain implementation, CQRS and fully event-driven on top of MassTransit with Azure service bus as the transport. All fully test-driven.
.net core web api
MiniSpa implemented using Aurelia

Marco Damaceno • Feb 12 '22

Rails 7

FJones • Feb 9 '22

Weirdly, much as I love django, I'm going with an express + react stack. Much easier to handle, and code sharing is excellent. No typescript, though.

Anders • Feb 10 '22

.Net 6 / PostgreSQL. Vanilla JS.

Pan Chasinga • Feb 10 '22

Probably Next.js, Rust (Rocket), and PostgresDB.

Jonathan pick • Feb 10 '22

React, nest.js, rabbitmq, redis,
K8s, Argo - cd, workflows ( for pipelines ), rollout for releases, kube Prometheus stack for monitoring / alerting, kubevela to ease the pain of helm charts. That’s a company not a site.

Jun Le • Feb 9 '22

React Native, Firebase. You can spin up a CRUD type app (E-commerce or similar things) on web + mobile in less than a day.

Dwayne Charrington • Apr 12 '22

Frontend: Aurelia 2 + Shadow DOM for component sytle encapsulation.
Backend: Supabase

Mike Rispoli • Mar 9 '22

Nx
NestJS (backend)
NextJS (frontend)
Fauna if NoSql or Postgres if Sql (database)
Typescript everywhere

hadezuka • Mar 8 '22

maybe for frontend i'll use vue/nuxtjs and for backend using nestjs with postgres or using supabase.

Herat Patel • Mar 8 '22

Frontend: React / Next
Backend: Go / Node / Firebase Cloud Functions

Moritz Müller • Mar 6 '22

Frontend: Vue 3 + Tailwind
Backend/Auth: .NET 6, Auth0, Postgresql

Liviu Lupei • Mar 6 '22

frontend: React and GatsbyJS
backend: Node
infra: AWS EC2 mostly
testing: endtest

Binh Huynh • Mar 5 '22 • Edited

Frontend: EJS, Bootstrap, JS
Backend: NodeJS, ExpressJS

Camilo • Feb 20 '22

Backend: Elixir + Phoenix Live View
Frontend: Tailwind, Bulma or Bootstrap

Graham Morby • Feb 16 '22

Front end : Vue.Js 2 and tailwind
Backend: python flask
Database : either straight up MySQL or mongo

It’s a good combo

Brian King • Feb 16 '22

Devend: VS Code, Node, Git
Frontend: NuxtJS, TypeScript, TailwindCSS
Remote Repo: GitHub
Host: Netlify with AWS Lambda OR Cloudflare Pages with Cloudflare Workers
Database: Fauna OR DGraph OR Neo4j

Franco Correa • Feb 16 '22

I am working on a side project with blitz right now and it's freaking awesome

Hassan Schroeder • Feb 16 '22

Elixir/Phoenix, of course 😀

metacollective • Feb 15 '22

Frontend: nextJS or PReact + Tailwind
Backend: Serverless (lambda) + Postgres (on AWS aurora, serverless again)

miku86 • Feb 14 '22

Django, Tailwind

If there has to be some fancy frontend stuff, probably React or Vue with Typescript.

Paweł Świątkowski • Feb 14 '22

I'm afraid I know too little about Etsy and about dogs, not to mention these two in common, to make a solid decision about tools most fitting for the job.

Zizaco • Feb 13 '22 • Edited

AdonisJS + InertiaJS (Vue3)

codart1 • Feb 13 '22

It depends, but assume that it's relative simple or a pet project then I will pick:

sveltekit or solidjs
deno for the backend Of course, can't live without typescript

Josef Held • Feb 12 '22

Backend: MeteorJS (DB: MongoDB)
Frontend: ReactJS

Rudy A. Hernandez • Feb 12 '22

AMEN 🙏 (Angular, Mongo, Express, Node) stack

theMightiestT • Feb 12 '22

Alpine or plain JS on the front end for sure

probably Vue should the need arise - but only if.
- Node, graphql, and services on AWS.

Boris Jamot ✊ / • Feb 12 '22

HTML/CSS + Golang + Postgres

Davis Tibbz • Feb 12 '22

Vue + TS Front;
Springboot backend;
MySQL: DB

Davis Tibbz • Feb 12 '22 • Edited

Vue3 + TS + Element Plus: Front
Springboot: Backend
MySQL: primary DB
Redis: Cache and Sessions

Frank Szendzielarz • Feb 10 '22

Blazor, C#/.NET, Azure Web Apps, Azure SQL

Raj • Feb 11 '22

Linux + ASP.NET Core + MongoDB using Vscode (All Open Source + Free Development Environments)

redicrafty • Feb 12 '22 • Edited

I used to create apps using preact, but now am in love with svelte.

Frontend: Svelte + Tailwind CSS
Backend: Python Flask/Django
Database: some SQL db

AdhirajBhatia • Feb 12 '22

Frontend : Remix.js
Backend : Prisma & Postgres
Styling : Tailwind CSS

This is the most easy and powerful stack I have ever used !

Emanuel Quimper • Feb 11 '22

Go + Postgres + NextJS + Tailwind

Javier Guerra • Feb 11 '22

This days I am all about PhoenixFramework + Live View, haven't get into Tailwind yet, but not sure I will, I will like to try BEM though

Jonathan Boudreau • Feb 11 '22

react, ant design, stripe, auth0, fastapi, and postgres.

Stephanie Handsteiner • Feb 10 '22 • Edited

PHP /w Symfony on the backend
Vanilla HTML, CSS, JS (well tbh this will most likely be TypeScript) on the Frontend
Postgres for the Database
RabbitMQ or Redis as a message broker

Dimitrios Desyllas • Feb 10 '22

The one I need ASAP to know in my paid job. I mean If I need to do something ASAP why not try invensting my time into something that will aid me to make my daily wage?

ShaileshNayak-ops • Feb 10 '22

PEVN Stack is unbeatable

Ivan Jeremic • Feb 10 '22

Cheap Sleeper stack is WordPress backend and a WP theme which is installable trough wordpress but has interactive parts built with react and block editor blocks.

Anshuman Bhardwaj • Feb 10 '22

Next.js with tailwindcss is my goto. I recently made blog using that. Remix is also something I'm excited about.

Karan Pratap Singh • Feb 10 '22

Next JS (with TypeScript) + Antd, Go (backend), GraphQL (API Layer), AWS EKS, Github Actions (CI)

𒎏Wii 🏳️‍⚧️ • Feb 10 '22

Tarantool + Openresty + A bunch of javascript from my github. I wish I was joking.

Matteo • Feb 10 '22

Anybody uses storybook for development?

Valeria • Feb 10 '22

I'd use SvelteKit with Cloudflare pages adapter for SSR PWA. If this wouldn't be enough on its own - I'd use Encore (Go+Postgresql) deeper in the stack and whatever additional microservices I'd need.

Sanna Jammeh • Feb 10 '22

I generally rotate this depending on criteria:

Front end:
React + stitches / tailwind

Backend:
Next.js
Nest.js

DB & Auth:
Firebase
Supabase
NextAuth and postgres

Luca Argentieri • Feb 9 '22

I'm trying Prismic with Next and scss

James Moore • Feb 9 '22

Laravel :) !

Juan Vega • Feb 15 '22 • Edited

Deployment: A container runner, heroku, fargate. Flexibility with low effort
Database: Postgress
Back: Kotlin
Front:js+react+styled components
Auth: okta/Auth0