Startups and tech enthusiast. Loves building products that make your life easier. Currently, building Qovery - a platform revolutionizing application deployments in the cloud.
Actually it really is not a mono repo, let me just start over on that one.
Think any plug in platform, like Jenkins. We have the platform, it has its own development team and release.
We then have components which have their own repo. Finally we have the repo which I was talking about. It uses the nuget packages from the components, supplies their configuration and wire up into the platform.
So no not really mono and not really separate applications.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Is your backend just one application? Or it's a set of micro apps in one repository?
Actually it really is not a mono repo, let me just start over on that one.
Think any plug in platform, like Jenkins. We have the platform, it has its own development team and release.
We then have components which have their own repo. Finally we have the repo which I was talking about. It uses the nuget packages from the components, supplies their configuration and wire up into the platform.
So no not really mono and not really separate applications.