Why adopting a monorepo is a smart move for your organization
Adopting a monorepo approach means that the majority of the code and configurations for the project reside in a single repository. This leads to several benefits.
Simplifies code editing
Enables more frequent releases
Helps to produce new code faster
Integrates multiple technologies
Monorepo consulting services
We know how to navigate and respond to the challenges of working with monorepos. Our engineers have experience in migrating projects using every major tooling (e.g. CMake, Maven, and Gradle), particularly with large codebases.Monorepo migrations
- Streamlining the process of building, testing and releasing your software.
- Adopting the industry-standard tooling and practices.
- Securing your build from supply chain attacks.
- Updating your security to match industry standards.
- Optimizing build time and reducing CI/CD costs.
Monorepo consulting and strategy
- Assessment of your existing code.
- Building custom monorepos.
- Simplifying your build and developer tooling.
- Onboarding for your new developers.
Why is Bazel the best choice for monorepos?
Bazel is a tool dedicated to monorepos that allows for faster loading times. Its architecture supports massive scalability, ideal for large projects and distributed teams. Migrating to Bazel minimizes friction and makes your builds faster, more secure, and scalable across multiple languages and platforms.
Take advantage of Bazel migrations and elevate your development process.
Achieve up to 10 times faster build times and faster code compiling.
Improve your security with reproducible builds.
Save the costs of running your CI infrastructure.
Accelerate development cycles with remote execution.
Enhance your code’s reusability and reduce its dependencies.
Offers better control over your project.
The Bazel migration process
We start by determining which areas will benefit the most from the Bazel migration. After careful assessment, our engineers suggest the most appropriate out of 3 approaches.
1. An immediate migration.
We select an optimal time to freeze non-critical updates to the old system. This allows our team to start migrating your project to Bazel. Meanwhile, we will continue to maintain your existing tooling, ensuring a stable development environment.
2. An integration layer approach.
The migration is gradual and is achieved by integrating the old build system into the new one (or vice versa). For example, initially, the first 80% of your project will use your old build, and the remaining 20% will be Bazel-based, but your developers will interact only with Bazel. Over time, the balance will shift until your tooling becomes 100% Bazel-based.
3. Maintaining parallel builds.
Bazel as well as your old tooling are run and maintained simultaneously. Our team manages the Bazel build and migrates changes done to the old build system. Developers and releases pipelines will be moved gradually to the Bazel build.
Every migration process looks different, depending on the approach and each client. As a result, the codebase is built faster, in a more secure manner, and with fewer resources.
Every migration process looks different, depending on the approach and each client. As a result, the codebase is built faster, in a more secure manner, and with fewer resources.
Bazel and Monorepo's success stories
1
Achieved fewer disruptions and more stable development environments.
2
Simplified adoption of new tools and setup.
3
Improved productivity and decreased coding errors.
C++ integration in Bazel monorepos
1
Streamlined maintenance across our client's multinational operations.
2
Improved scalability of the employee platform.
3
Improved User Interface.
Employee self-service portal
1
Enhanced the development environment.
2
Ensured code quality and consistency.
3
Made the integration process more efficient.
Upgrading the development tooling with Bazel
Bazel integration
We can help you integrate Bazel with your technical stack, regardless of the technology you are using.Integration
- Multi-langage support
- Caching
- Remote execution
- Custom Bazel rules and toolchains
- Reliable IDE integration
Consulting
- Troubleshooting
- Performance optimization
- Build analysis
- Training and mentoring for your development teams
Maintenance and optimization
- Developer Experience as a service
- Developer support
- Metrics & Monitoring
Meet our experts
Krzysztof Romanowski
Head of Tooling
Łukasz Wawrzyk
Bazel & IDE expert
FAQ
Can I migrate to Bazel myself?
Yes, you can. However, compared to similar tooling, Bazel is non-standard, and its migration process can take different paths for each project. With our experience, we will propose the most efficient path, tailored to your codebase and organization.
Why is Bazel VirtusLab’s recommended tooling?
Bazel is derived from tooling created at Google, created to reliabliy build of the biggest codebase ever created. We've used it for years, with great results. It has a growing community and is being used by many large companies word-wide. When it comes to monorepos, Bazel is a gold standard and we believe that it will continue to be a market leader.
Bazel focuses on performance, correctness, and security, which are key aspects for tools used to build large projects. Bazel has a reputation for complexity, but with our expertise, we can make it the foundation of your project's success.
Does monorepos have any drawbacks?
The biggest drawback of monorepos is related to their size—without proper setup, monorepos are slow to work with. Their size puts a strain on tooling and can often overwhelm developers. This is when experience and expertise are needed, as a properly set up monorepo can be as fast and responsive as any other project from a developer's perspective.
Would Bazel work with my tech stack?
Most likely. Bazel comes with a wide selection of rules, allowing it to build almost all popular languages and technologies. Bazel features an extensive system for extensions, making it possible to integrate with any technology used in a project.
Thanks to features like remote build execution and caching, Bazel can replace some of the expensive and error-prone tools used in your project.
Will my team need special training?
Bazel requires specialist knowledge to manage it properly. We provide training for your development team, so they can use it effectively.