michael-s-molina commented on PR #34826: URL: https://github.com/apache/superset/pull/34826#issuecomment-3879173134
> I generally agree, these are valid concerns. But, on a generic web app, connection pooling is highly desirable, same logic applies up to a certain extent here. @dpgaspar I completely agree that connection pooling is a valuable and highly desirable feature. The points raised by @villebro and myself are more about how we should introduce this feature into Superset. Currently, Superset operates in at least two modes: - A basic mode where Celery and Redis are not available - An advanced mode where Celery and Redis are available, enabling distributed operation In recent efforts—such as [GTF](https://github.com/apache/superset/pull/36368)—we’ve ensured support for both modes, so organizations of any size or setup can benefit from new features. To illustrate the alternative: @villebro could have designed GTF to function only in distributed environments, making Celery and Redis mandatory. Perhaps we need a broader conversation about which modes of operation we officially support, and whether new features should be compatible with all modes. I propose we discuss this further on Friday's Town Hall. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
