When it comes to microservices, do you put each microservice in it's own git repository, or use a monorepo? If the same, how do you handle multiple services in the same repo? Keen to hear your thoughts

• ASP.NET Core

  1,632 34,312 9.9 C#

  ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.

  

The examples you cited ASP.NET Core and DotNet Runtime are in fact great examples of repos which are singular in their purpose. I wouldn't call them 'monorepos' at all unless one takes that term to mean a "repo which many different teams/orgs use". Is that what you meant? I sure didn't. The author of the article says that repos should be "about work culture and communication". I guess that means that if we both use a repo but work in different cultures, that we should fork our own copy of the repo? I'll disagree entirely. That clearly wouldn't work for the more famous examples like ASP.NET Core.

• .NET Runtime

  607 14,091 10.0 C#

  .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.

  

The examples you cited ASP.NET Core and DotNet Runtime are in fact great examples of repos which are singular in their purpose. I wouldn't call them 'monorepos' at all unless one takes that term to mean a "repo which many different teams/orgs use". Is that what you meant? I sure didn't. The author of the article says that repos should be "about work culture and communication". I guess that means that if we both use a repo but work in different cultures, that we should fork our own copy of the repo? I'll disagree entirely. That clearly wouldn't work for the more famous examples like ASP.NET Core.

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project