top | item 40381682

(no title)

whodev | 1 year ago

Guess it depends on your definition of a mono-repo vs multi-repo. I'd consider what we have as a mono.

We have one repo which is our main web application (user dashboard, landing page, etc..), our API, and our scheduled tasks. With how much code is shared between these services it just makes sense to keep them together.

We then have separate repo's for other services that aren't critical or apart of what was mentioned above.

discuss

order

No comments yet.