> The shared libraries made building new destinations quick. The familiarity brought by a uniform set of shared functionality made maintenance less of a headach

> The shared libraries made building new destinations quick. The familiarity brought by a uniform set of shared functionality made maintenance less of a headache. > However, a new problem began to arise. Testing and deploying changes to these shared libraries impacted all of our destinations. It began to require considerable time and effort to maintain. Making changes to improve our libraries, knowing we’d have to test and deploy dozens of services, was a risky proposition. When pressed for time, engineers would only include the updated versions of these libraries on a single destination’s codebase. When pressed for time, engineers would only include the updated versions of these libraries on a single destination’s codebase. I think I see the problem and it wasn't with microservices.