home.social

#monorepos — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #monorepos, aggregated by home.social.

  1. Monorepo vs. Multi-Repo vs. Git Submodule vs. Git Subtree: A Complete Guide for Developers, by (not on Mastodon or Bluesky):

    archive.ph/AHiTd

    #guides #architecture #monorepos #git #versioncontrol #comparisons

  2. Monorepo vs. Multi-Repo vs. Git Submodule vs. Git Subtree: A Complete Guide for Developers, by (not on Mastodon or Bluesky):

    archive.ph/AHiTd

    #guides #architecture #monorepos #git #versioncontrol #comparisons

  3. #Monorepos bei Uber: 👍 oder 👎?
    #SoftwareArchitektur im #Stream
    Freitag 2025-09-26 13:00 CEST
    Mehr Informationen und Möglichkeit für Fragen:
    software-architektur.tv/

  4. #Monorepos bei Uber: 👍 oder 👎?
    #SoftwareArchitektur im #Stream
    Freitag 2025-09-26 13:00 CEST
    Mehr Informationen und Möglichkeit für Fragen:
    software-architektur.tv/

  5. Moving from #Java 7 to 8 at #Twitter was a long and painful process (I blame #Monorepos) and we ended up backporting features like #JVMCI from Java 9 to Java 8 because it was easier than migrating the whole service graph to the newest release.

  6. Moving from #Java 7 to 8 at #Twitter was a long and painful process (I blame #Monorepos) and we ended up backporting features like #JVMCI from Java 9 to Java 8 because it was easier than migrating the whole service graph to the newest release.

  7. Frustrated with CircleCI for Monorepos?

    You're not alone. It's not Mavrick Laakso's favorite either -- but it makes sense for his current client.

    “And so, dear reader, I have identified and navigated all the foot-guns and false-starts so that you may learn from my begrudging, grumbling hours spent accomplishing this task using my not-favorite CI/CD tool.”

    See his easy tips on the blog: link.testdouble.com/jxm

    #CircleCI #Monorepos

  8. Frustrated with CircleCI for Monorepos?

    You're not alone. It's not Mavrick Laakso's favorite either -- but it makes sense for his current client.

    “And so, dear reader, I have identified and navigated all the foot-guns and false-starts so that you may learn from my begrudging, grumbling hours spent accomplishing this task using my not-favorite CI/CD tool.”

    See his easy tips on the blog: link.testdouble.com/jxm

    #CircleCI #Monorepos

  9. I'm going to go against software engineering orthodoxy, on a couple of topics:
    1. Monorepos
    2. Trunk-Based Development.

    There ideas can be particularly toxic to small startups when taken as gospel truth.

    #softwareengineering #git #monorepos #trunkbaseddevelopment

    (Image credit: Microsoft Designer AI with the prompt: "A diagram of a git workflow with a datacenter server in the background"

  10. I'm going to go against software engineering orthodoxy, on a couple of topics:
    1. Monorepos
    2. Trunk-Based Development.

    There ideas can be particularly toxic to small startups when taken as gospel truth.

    #softwareengineering #git #monorepos #trunkbaseddevelopment

    (Image credit: Microsoft Designer AI with the prompt: "A diagram of a git workflow with a datacenter server in the background"

  11. Dive into the world of #monorepos with Juri Strumpflohner in this #InfoQ talk!

    Gain valuable insights on how to go from a "monorepo mess" to "monorepo bliss": bit.ly/46YfECg

    Learn what monorepos are, why they're beneficial, and how to set them up to be successful in the long run.

    #QConLondon

  12. Dive into the world of with Juri Strumpflohner in this talk!

    Gain valuable insights on how to go from a "monorepo mess" to "monorepo bliss": bit.ly/46YfECg

    Learn what monorepos are, why they're beneficial, and how to set them up to be successful in the long run.

  13. Wondering about the differences between #Monoliths, #Monorepos & #MicroFrontEnds?

    👀 Watch this #InfoQ talk by Ruben Casas on the evolution of frontend applications at scale.

    Explore each approach’s pros & cons and choose the best tool to help you scale your applications: bit.ly/3EIBygj

    #FrontendArchitecture #WebDevelopment

  14. Wondering about the differences between , & ?

    👀 Watch this talk by Ruben Casas on the evolution of frontend applications at scale.

    Explore each approach’s pros & cons and choose the best tool to help you scale your applications: bit.ly/3EIBygj

  15. Begleite uns in die CI/CD-Welt. Christian Schlatter hat sich mit komplexen #Pipelines, schwer fassbaren #Debugging-Szenarien und den Besonderheiten von #Monorepos auseinandergesetzt und teilt seine Erfahrungen in der ersten Episode einer dreiteiligen #Blogpost-Serie. 🛠️ 🌍 #CICD #TechJourney #legacy

    puzzle.ch/de/blog/articles/202

  16. @marick Yes, have advantages, but are not without downsides:

    * tags apply to the whole repo, which is awkward for versioning and releasing independent artefacts
    * carbon/money costs can be relatively high when "safe" changes, e.g. to docs or website, trigger expensive CI checks
    * all or nothing in terms of private/public,
    access control (e.g. limiting write access to certain subcomponents), issue management, fork maintenance, and continuous deployment

  17. @marick Yes, #monorepos have advantages, but are not without downsides:

    * tags apply to the whole repo, which is awkward for versioning and releasing independent artefacts
    * carbon/money costs can be relatively high when "safe" changes, e.g. to docs or website, trigger expensive CI checks
    * all or nothing in terms of private/public,
    access control (e.g. limiting write access to certain subcomponents), issue management, fork maintenance, and continuous deployment

  18. Question for people using #MicroFrontends and #Monorepos: What do your #integration tests look like?

    The #Google model of monorepos always builds everything at HEAD, but doing so would not catch version skew issues that come with independent deployments. That implies that your integration tests _cannot_ just build and run everything at HEAD, you actually have to deploy each change individually to a staging environment and alert on failures.

    That feels like a much more complex setup than I'm used to seeing for integration tests. Do people actually do this or is version skew a giant blind spot for microfrontend testing?

  19. Question for people using and : What do your tests look like?

    The model of monorepos always builds everything at HEAD, but doing so would not catch version skew issues that come with independent deployments. That implies that your integration tests _cannot_ just build and run everything at HEAD, you actually have to deploy each change individually to a staging environment and alert on failures.

    That feels like a much more complex setup than I'm used to seeing for integration tests. Do people actually do this or is version skew a giant blind spot for microfrontend testing?

  20. We've created an official feed for Rush Stack, a collection of open source build tools for large scale ! If you use Mastodon and tooling, follow us to show your interest!

  21. Does anyone have a ELI5 for the trend towards now? Not even 4 years ago we were moving AWAY from monolithic structures, now we're moving back??

  22. Does anyone have a ELI5 for the trend towards #monorepos now? Not even 4 years ago we were moving AWAY from monolithic structures, now we're moving back??