It depends if your application needs them to be the same. If they have different reasons for change, you're going to add more headaches by duplicating it. And like a lot of tisico sympathy for the future, when i talk about maintainable ato robust code,. Youd have ampathy for those future maintainers. Put yourself in their shoes. Are they going to want to mibrate some time and maybe change the api that they present to customers, or uwsers or other developers? Do you want to change your data base at the same time? If so, keep them t heif you want to keep that separate so that you have certain migration paths, maybe