potiuk commented on issue #27292: URL: https://github.com/apache/airflow/issues/27292#issuecomment-1550173096
Just also to explain why - there was a bit of a story few days back about Aamazon going back to smarter monolyth from microservices https://thenewstack.io/return-of-the-monolith-amazon-dumps-microservices-for-video-monitoring/ and this goes hand-in-hand with my observations (and the reason why we still have monorepo for airflow and providers). Splitting up into pieces looks cool but in a number of cases it is not a "golden bullet" while it adds isolation and decouples stuff, when there are hidden couplins, it might bring way more cost than it brings benefits- maintaining and solving problems coming uf with such a split might easily cost more than potential benefits. So once we get rid of the root cause of the problem (which in fact was not very related to the internal google package structure but more to the fact that we had "half-baked" cake, then we should carefully see what are the needs and cost of any splitting approach and see if any of that is needed. IMHO we should not discuss `splitting vs extras` but `extras vs. doing nothing` at most. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
