Usually NodeJS with express and nextjs for the backend, React (usually just styled-components) for the frontend. Database choice depends on the project, but mostly postgresql (I avoid NoSQL where possible).
With servers I avoid AWS since the costs seem excessive to me + once you how to setup one server you know how to setup every server. For the hosting provider it's usually Hetzner since I haven't found a better value/$ provider.
Also TypeScript everywhere!
Backend Hosting: AWS Lambda, Digital Ocean droplets
CI/CD: GitHub actions
Honestly though, most of the time what you already know is best. The only excepts are things like python for AI, etc. where the specialization/community of the language matters.
I stick with jamstack templates for most of my MVP's. Ive curated a huge list of apps from Gatsby, Next, using Netlify. My "goto" stack is NodeJS/React-based only because it's my stack for work. Many other utils and frameworks almost never default. With new tools always emerging, I only include anything else (even sql) after making sure I understand what I need.
TALL Stack - Laravel, TailwindCSS (With JiT compiler), a sprinkle of Livewire components and a dash of AlpineJS for dropdowns, etc.
I've been using VueJS and others for a few years and recently went back to pure Laravel/non-js coding and it's amazing how much quicker and less of a headache it is. Don't get me wrong JS frameworks are great and open a lot of possibilities, but sometimes pure PHP/Blade just gets the job done and shipped faster.
Hey Leo, this is my tech stack on my project.
I'm keeping it simple by using Google Firebase for everything:
I've just recently release my SaaS product recently and publish the tech stack I used to build it: https://creativedesignsguru.com/saas-tech-stack/
I like to keep my tech stack simple
Hey Leo,
My stack is the following:
Usually NodeJS with express and nextjs for the backend, React (usually just styled-components) for the frontend. Database choice depends on the project, but mostly postgresql (I avoid NoSQL where possible).
With servers I avoid AWS since the costs seem excessive to me + once you how to setup one server you know how to setup every server. For the hosting provider it's usually Hetzner since I haven't found a better value/$ provider.
Also TypeScript everywhere!
I’m building a native, cross-platform app with Racket! It automates creation of static sites on AWS with S3, Cloudfront, Lambda, and Cognito.
Bootstrap for the frontend
Memberstack/Integromat/DigitalOcean/Cloudflare Workers for the backend
google sheets/basecamp for admin work
http://submark.co
In no particular order:
In general tech stack is dependent on the project's needs and mostly I use the tools I'm experienced in.
Next.js + Chakra-UI + Hasura + Expressjs
bubble.io
nice!
Woohoo! Tech stack:
Honestly though, most of the time what you already know is best. The only excepts are things like python for AI, etc. where the specialization/community of the language matters.
I stick with jamstack templates for most of my MVP's. Ive curated a huge list of apps from Gatsby, Next, using Netlify. My "goto" stack is NodeJS/React-based only because it's my stack for work. Many other utils and frameworks almost never default. With new tools always emerging, I only include anything else (even sql) after making sure I understand what I need.
TALL Stack - Laravel, TailwindCSS (With JiT compiler), a sprinkle of Livewire components and a dash of AlpineJS for dropdowns, etc.
I've been using VueJS and others for a few years and recently went back to pure Laravel/non-js coding and it's amazing how much quicker and less of a headache it is. Don't get me wrong JS frameworks are great and open a lot of possibilities, but sometimes pure PHP/Blade just gets the job done and shipped faster.