The DRY principle of Don’t Repeat Yourself has been one of the commandments of software engineering, ever since The Pragmatic Programmer book in 1999. A lot of things have changed since 1999, however. Microservice Architecture is directly questioning supremacy of “reuse”, advocating to prioritize “replaceability and upgradeability over reuse”. We will explore whether reuse of code, model and design are still always a good idea, especially in large, enterprise applications built with a microservice architecture. We will provide concrete guidelines that we have used in our work to decide when reuse should be prioritized vs. de-prioritized.