Let's assume we've convinced you that Polylith might be a good idea. Perhaps you're even thinking about converting one of your projects to Polylith, so you can try it out for yourself. If so, that's awesome!
However, you might also be feeling a little worried about the risks with trying a new architecture. What if it looks good in theory, but doesn't work in practice?
The Polylith team has been building production systems with Polylith for two years, and so far we've only had positive experiences.
As of this documentation going live, there are six Polylith projects in production. All of them are built in Clojure and use the Leiningen version of the Polylith Tool.
These projects range in size and complexity, from a complete recruitment platform to a simple web application. These projects have taught us that components are a powerful tool to fight complexity in services of any size. Building services with Lego-like blocks turned out to be even faster, easier and more enjoyable than we dreamed!
Polylith is an inherently scalable architecture. That's because a single Polylith workspace can be shared by multiple teams, and offers flexibility on how we can collaborate on our bases, components, services and systems. Polylith allows us to work together in a controlled and confident manner, because every change is tested against all affected services and building blocks within the workspace.
We hope that large teams decide to give Polylith a try, but we're excited to support it in projects of all sizes!