Project structure ?
Tl;dr: Company has given me a difficult task that doesn't make sense for a junior, and I have 2 months to prepare. Now I'm working on the project assigned to him (Manager said it's a small project). I planned to use Turborepo; Astro with React and Tailwind for the frontend and Express, trpc for the backend.
I want to know if there's a practical project architecture for this case, and whether should I leave the company?
11 Replies
out of curiosity, why do you want a separated backend? especially if your using react, why not use next?
The project is about building a dashboard, so we already got a seperate db for querying, and my long term career goal is to be a fully capable fullstack dev, so I'm expecting myself to be able to work on a separate backend so there's that
next isnt a db
you would still query your db from next
or whatever data fetching you need to do
and next is very much full stack
youll be doing the same sort of code that you would in a separated stack, just way easier, and create a better end product
if its a simple dashboard site, yeah you should be able to spin that up with next very, very fast
feel free to even use my boilerplate. Its basically t3 but with a bunch more batteries
GitHub
GitHub - GentikSolm/t3-app-dir: t3 app dir boilerplate
t3 app dir boilerplate. Contribute to GentikSolm/t3-app-dir development by creating an account on GitHub.
yeah sure, why not, I've been trying to balance between learning a new skill (be it backend dev and/or devops) and meeting expectations for this time being
you dont want to go too far into the deep end / complex shit. Learn a few new tools at time
doing k8s, docker, separated stacks, etc is a massive amount of stuff to learn
docker alone took me a year to really get good at and i still only use it if i really need to because of how much complexity it brings
I thought t3 natively supports
app dir now, so is that boillerplate like another combination of the suggested tools for the t3 stack ?it does. i built that before they released it. read the readme for mine
Well, actually for my case rn I don't think the stack really matters that much, it's more about how I organize the project so that it can be deployed from gitLab (since that's what my company uses)
So if I'm using Next, isn't it also a monorepo ?
Here's the thing, my team actually has a somewhat devops/system kinda guy, and he's been protesting against monorepo architecture, making the case that what if I have a commit that ONLY updates the backend, and the frontend should not be affected while the pipeline is building that newly updated thing for that backend.
And it seems like using Next falls right in the case that he's worrying about, so now I can't really persuade him to build a ci/cd flow for that
Yes, mono
How many people are using this dashboard?
If you use next just throw it on Vercel and call it a day
If you use vercel, it isn't. If you make a commit that purply changes your BE, your frontend doest change. Hell all Vercel updates are purely in place, w/ zero downtime
alright, I'll try to persuade him to give it go at vercel. Our biggest concern is the price tho. We'll assess and see if Vercel's free tier is applicable