4 ms·
What about a single product with multiple components though? Let's say you have an API and a browser client (SPA). Should you keep them in the same repo, or sep
by enraged_camel 8y ago
What about a single product with multiple components though? Let's say you have an API and a browser client (SPA). Should you keep them in the same repo, or separate them?
So far the only good reason I've had for separating them has been related to deployment concerns (e.g. your API is deployed to AWS and your browser client is on Cloudflare).
- royjacobs 8y agoIf you have an API and a SPA that's tightly coupled then, yes, same repo. If your API is a separate product with a separate release cycle, proper testing and backwards compatibility checks, then different repo.