Block's 450 JVM Repo Monorepo Shift

Monorepo at Scale: Block's Dependency Drift Solution

Block's successful migration of 450 JVM repositories to a monorepo highlights a common pain point in large-scale software development: dependency management and coordination complexity. The article effectively articulates the challenges of a polyrepo model, such as dependency drift, duplicated upgrade efforts, and runtime incompatibilities, and showcases how a monorepo, coupled with custom tooling and disciplined practices, can address these. The emphasis on atomic updates, direct source dependency resolution, and the custom IntelliJ plugin for developer experience are particularly noteworthy. The insight that AI-assisted development tools thrive in a high-context monorepo environment is a forward-looking observation, suggesting that monorepos might become even more advantageous with the rise of AI coding assistants.

However, the article also implicitly points to the significant investment required for such a transition. The mention of custom IntelliJ plugins, sophisticated Gradle configurations, merge queues, and the need for a dedicated platform team underscores that a monorepo is not a silver bullet. It demands substantial engineering effort and ongoing commitment. The advice against monorepos for projects with vastly different languages/frameworks or when a platform team cannot be adequately funded is crucial. The migration's extended timeline due to CI scalability challenges and the effort needed to optimize legacy, custom-setup polyrepo projects serves as a cautionary tale. While the benefits are clear, organizations considering this path must be prepared for the inherent complexity and resource allocation required to make it successful.

Key Points

• Block migrated ~450 JVM repositories from a polyrepo to a monorepo to combat dependency drift and coordination issues.
• The monorepo enables atomic updates across services in a single commit and resolves shared dependencies directly from source.
• Key enablers include a custom IntelliJ plugin for optimized IDE workflows, merge queues for main branch stability, dependency graph-based build scoping, and Git performance tuning.
• The migration improved developer experience, leading to faster CI times (p90 around 10 mins) and a more cohesive codebase.
• Block advises against monorepos if a dedicated platform team cannot be funded or if projects have vastly different languages/frameworks.

---

📖 Source: Behind the Scenes: Block 450 JVM Repositories Into Monorepo to Reduce Dependency Drift