Really curious to know about the technology choice, why you went through the mentioned techstack and how should someone who is building their first product decide this? Great content as always.
Go with what you know. Every project I use a slightly different stack. It allows me to learn new tools and stay up to date. Also tools change over time. One thing that's been common to all my projects is that they're full-stack JS (and the last few years they're all full-stack TS. And also all use React). There are a lot of good ways to build things. But a quick summary: Next.js - backend and frontend in one repo with minimal set up. Very easy to deploy to Vercel. React - used it for years. Most popular frontend framework by far. That makes it easy for others to join the project too. Widest base to pick from (same goes for the entire stack TBH). Nothing wrong with Vue or Svelte or HTMX or whatever you feel comfortable with. Tailwind - again it's the default these days. Has a nice set of defaults with Shadcn/ui and Tailwind UI. Postgres - default SQL db. Prisma - other options are Drizzle and Kysely. Maybe I'll try one of those on another project. Tinybird - nice solution for analytics. In hindsight it may not have been the best choice for this project and we may move away from it in places. Redis - not absolutely necessary. Usually I'd recommend sticking to one database where you can. For new projects I'd consider Supabase as well. Although never used it. Something I try to avoid is using frameworks that may disappear one day. It's annoying to be using deprecated projects that no one uses anymore. I have an old project on Meteor which that happened to. A lot more I could write but hopefully gives you an idea.... No right and wrong. Great apps written in PHP and jQuery too. Do what works. What are you considering using?
@@elie2222 Hey, Thanks for such great explanation. I'm exploring a concept for a community-driven platform that facilitates referrals and talent showcase, connecting educators, learners, and recruiters. And, the techstack i'm moving forward with is frontend: next js with shadcn and taiwlind backend: express js, monorepo, trpc, and prisma for db, might use redis for invite system and caching. The one thing i'm not sure about is the authentication part. Since, the product will be mostly free, i don't want to spend alot of money. Any suggestions?
![Felix "Unfair" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/Oswujxm2Ag0/mqdefault.jpg)
![Seungmin "그렇게, 천천히, 우리(As we are)" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/kAzmhLHePqU/mqdefault.jpg)
Really curious to know about the technology choice, why you went through the mentioned techstack and how should someone who is building their first product decide this? Great content as always.
Go with what you know.
Every project I use a slightly different stack. It allows me to learn new tools and stay up to date. Also tools change over time.
One thing that's been common to all my projects is that they're full-stack JS (and the last few years they're all full-stack TS. And also all use React).
There are a lot of good ways to build things. But a quick summary:
Next.js - backend and frontend in one repo with minimal set up. Very easy to deploy to Vercel.
React - used it for years. Most popular frontend framework by far. That makes it easy for others to join the project too. Widest base to pick from (same goes for the entire stack TBH). Nothing wrong with Vue or Svelte or HTMX or whatever you feel comfortable with.
Tailwind - again it's the default these days. Has a nice set of defaults with Shadcn/ui and Tailwind UI.
Postgres - default SQL db.
Prisma - other options are Drizzle and Kysely. Maybe I'll try one of those on another project.
Tinybird - nice solution for analytics. In hindsight it may not have been the best choice for this project and we may move away from it in places.
Redis - not absolutely necessary. Usually I'd recommend sticking to one database where you can.
For new projects I'd consider Supabase as well. Although never used it.
Something I try to avoid is using frameworks that may disappear one day. It's annoying to be using deprecated projects that no one uses anymore. I have an old project on Meteor which that happened to.
A lot more I could write but hopefully gives you an idea.... No right and wrong. Great apps written in PHP and jQuery too. Do what works.
What are you considering using?
@@elie2222 Hey, Thanks for such great explanation. I'm exploring a concept for a community-driven platform that facilitates referrals and talent showcase, connecting educators, learners, and recruiters. And, the techstack i'm moving forward with is
frontend: next js with shadcn and taiwlind
backend: express js,
monorepo,
trpc, and prisma for db,
might use redis for invite system and caching. The one thing i'm not sure about is the authentication part. Since, the product will be mostly free, i don't want to spend alot of money. Any suggestions?
Amazing content! Appreciate you for sharing this type of information.
Thank you! What did you find most helpful in this one?
I have almost a year of coding in react and this looks scary to me. Maybe it is time I need to level up before its too late
What scares you?
@@elie2222 so many things starting with turbo repo iteself
Great content man!!
Thanks. What did you find most helpful?
How to build with modern and tending tech stack like shadcn ui, nextjs, tinybird.
Thanks for sharing.
Thanks for watching!
i am falling in love with you ❤❤❤❤
thanks! i wont tell my wife 😅
@@elie2222 😂😂