[rdslw]

Interesting third argument. Based on work by google and published papers, monorepos have some advantages. Of course not always and not everywhere.

But here, reddit connects it with service oriented architecture. Somehow i dont get it.

[pbiggar]

I think google might be the only people to do monorepo (and even they don't - for example, Android and Chrome are different repos), but they have built massive internal tooling to support this. For everyone else, once you get past a certain size, it's much much easier to do multi-repo than monorepo.

[ameliaquining]

Facebook also has a monorepo.

[ipsi]

As does Microsoft: https://blogs.msdn.microsoft.com/bharry/2017/05/24/the-large...

[ameliaquining]

I think that repo is just for Windows, not for everything Microsoft develops.

[vosper]

"just for Windows" probably still makes it one of the biggest repos in the world. I wouldn't be surprised at all if it's actually the biggest.

[ameliaquining]

It's definitely smaller than the Google monorepo.

[jonny_eh]

Possibly the oldest that is still in active use?

[latencyloser]

Correct. The project I work on at MS is 3 repos all by itself.

[mintplant]

Mozilla too.

[pbiggar]

No, it doesn't. Firefox is a monorepo (of course, it's just one product). All their other products (bugzilla, rust, all the web properties) have different repos. Check out their other repos: https://github.com/mozilla

[mintplant]

Many of those are synced back into mozilla-central (some bidirectionally, even).

> of course, it's just one product

In the sense that one package gets shipped to the end user, sure. But it's composed of many individual projects (SpiderMonkey, devtools, toolkit, layout...) which follow their own development paths and could each be broken out into their own repositories.

[pound]

as well as Twitter

[sgrove]

Also, JaneStreet

[pbiggar]

Are instagram and whatsapp in the same repo as facebook proper?

[julki]

Yes but web is separate from mobile

[julki]

There's actually a few different ones.

[alexchamberlain]

Personally, I buy into the 1 service, 1 repo argument. The fewer interferences between services the better.