Here’s a familiar story: A https://thenewstack.io/has-monolithic-architecture-gotten-a-bad-rap/ grows and grows to meet the https://thenewstack.io/what-to-do-when-you-dont-have-time-to-test-your-microservices/ and an https://thenewstack.io/how-to-support-a-million-users-on-your-website-a-success-story/. And one by one, unrelated product areas were decoupled and a distributed system was built in its place.

Yarn workspaces significantly decreased the time it took to ship changes and upgrade packages, however, the Commit-to-Publish timeline crept up again. LinkedIn Talent Solutions eventually migrated back to a distributed system while continuing to unitize yarn workspaces which allowed them to remain at a 97% time savings.

By co-locating the code within a single repository they were able to run package tests at the same time as application tests, ensuring compatibility with one another.

Related Articles