When building a full-stack project, is it best to keep both frontend and backend in the same repository or in separate repositories?

@fidexcode Short answer: It doesn't matter that much. There’s no single “best” choice, it depends on team size, project scale, and deployment style.

@fidexcode Separate I don't need to be looking at potential merge issues because a frontend dev fixed a button

@fidexcode It actually depends on the size of the project If you need simple and fast choose Monorepo and if you need scalability choose Polyrepo

@fidexcode From what I’ve learned so far, separate repositories help keep things clearer as projects scale. Still learning tho, open to other perspectives.

@fidexcode how many times will you post the same thing, bro ?

@fidexcode Keep it separately E get why

@fidexcode Always keep separate

@fidexcode It is better from maintainability PoV to keep the backend and the frontend code in the same repository. This simplifies making atomic commits, which change simultaneously the backend and the frontent and do not leave the repository in a broken state.

@fidexcode For me, a repository and, in general, any architectural design should reflect your development organization. If you have front-end and back-end development with different teams or clearly defined tasks between even just two engineers: so two repositories.

@fidexcode Monorepo until it hurts. Then split

@fidexcode Monorepo until your CI starts crying

@fidexcode I think there is no best choice it all depend For small projects, same repo works. For large scale projects or teams, separate repos are better for modularity and independent deployments.

@fidexcode monorepo addict until you die

@fidexcode Separate repos

@fidexcode Full stack with caffeine.ai

@fidexcode In the same project. For example with Java you could use Vaadin.

@fidexcode Better if separate. It's always cleaner and easier to manage. Also, if you want to assign someone to work only in Frontend/Backend, it will be straightforward to give them access without providing access to the other one.

@fidexcode Both included with the wonderful @caffeineai 🤩🙌 Have a go: Caffeine.AI Caffeine.AI

@fidexcode To have an opinion you can trust, actually build something. Unless of course you're trying to get engagement - which is fine.

@fidexcode Have a separate folder structure and use monorepo setup if you/your team are working on the same stack and are a few-member team, but the team wants flexibility, then separate repos are better for different languages.

@fidexcode Same repos! And ofcourse, dockerize if possible!!🐳💯

@fidexcode Start with monorepo: easier to split later than merge. Small team? Faster iteration & atomic commits. Scaling? Split when needed. But if separate devs and larger teams: separate works better

@fidexcode Next.js, I guess, recommends keeping everything in the same directory, but I use it only as a static frontend, with no serverless functions. My backend lives in a separate folder, usually in FastAPI, which I really like