No, thanks. Monorepos might be good for Google or Facebook where you have company-size teams to maintain all the tooling around them and there is no risk of "t

No, thanks. Monorepos might be good for Google or Facebook where you have company-size teams to maintain all the tooling around them and there is no risk of "the guy that did all the tooling left and now we don't know how this works anymore". You're not facebook, you're not google. Keep services on their own repositories, with their own pipelines, don't write internal libraries that reinvent the wheel, and if you do, just create them in their own repo and publish them as packages. Monorepos and all the associated bullshit is for teams which want to do technology for the sake of technology and for their resume. 90% of companies don't need monorepos, don't waste company's time and money because something is just fun to you.