IMHO, it’s an antipattern in almost every way. Being “common” doesn’t make it “smart”. The preprocessing argument is invalid for a lake, and the upfront “integration” time savings are cannibalized later by maintenance and risk overhead vs. proper service integrations. And everything you mentioned aside, there’s security and DPP risk. Lakes should not be used for collaboration between systems - that’s what lakeshore data marts are for, at worst, or real service-to-service APIs, ideally. (We have a good word for this in German: Datensparsamkeit. See also https://martinfowler.com/bliki/Datensparsamkeit.html). The people and services regularly using the lake should be data scientists and analytics folks, probably not prod services.