How to separate backend and frontend development?

Question

symfony

Hello!
There is a large project in which the backend and frontend are being cut by different groups of developers. How will their work be properly and effectively organized?
Git, Symfony2
1) one repository, but with submodules - for front-end developers (views, web folders)
2) different repositories
Share your advice and experience

Answer 1

Theoretically, of course, situations can arise when both the back and the front climb to edit the same place, in the same file, plus or minus at the same time. Which can lead to merge conflicts.
But, firstly, this should happen extremely rarely. Secondly, if this happens, then this is a matter of not quite correct processes or architecture. Thirdly, such conflicts are easily resolved by the team leader.
Therefore, I personally do not see any problem in the fact that the work goes to feature branches, each does its part, and then it's all merged.

Answer 2

Try a REST API, the front works with a well-standardized API, the backend doesn't care what it looks like.

Answer 3

I must say right away that I do not have much experience, but I will tell you how we do it.
We have a very small team. We mainly write web applications (CRM, etc.) using Laravel+Vue/AngularJS. We make one repository on BitBucket, distribute the rights and, as it were, everything. Backend-ers do not climb into the front code and vice versa. Therefore, no conflicts arise in the Gita. Well, if it arises, then there the git itself tells you what and how to do. Basically it's just git add * git commit -m "message". And all conflicts go away.
We do not experience any inconvenience with bitbucket. Again, you can bind the keys and not constantly enter the password. And everything works smartly.

Answer 4

There is a subtlety here in that the front-end team is, say, from the outside. A has access to the code of the entire project (and the project, I repeat, is large). But in general, a headache is when you have to organize the work of the front and back when changing templates

Answer 5

Monorepository, why complicate your life.