-
Notifications
You must be signed in to change notification settings - Fork 13.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(docs): create architecture page #28481
Conversation
This is ready for review. |
A Superset installation is made up of these components: | ||
1. The Superset application itself | ||
2. A metadata database to store Superset's data about users, charts, dashboards, etc. | ||
3. A caching layer (optional, but necessary for some features) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is called out twice in "components" and "optional component", i think it's a great idea to seperate the section, but let's have each component on just one side
hey! - I'm hoping it doesn't come across as a hostile takeover of this PR, but I threw your pages into GPT and added some comments/input in the form of bullet, and this is what came out: ArchitectureThis documentation outlines the architecture of Apache Superset, with a primary focus on the backend components before introducing the frontend. This organization provides a thorough understanding of how Superset operates from data handling to user interface. Superset BackendThe backend of Superset is composed of several critical components designed to manage data, execute tasks, and maintain the overall functionality of the system. Core Backend ComponentsWeb Application [Python/Flask]:
Metadata Database [Required]:
Optional Backend ComponentsAsynchronous Workers [Pytjhon/Celery]:
Caching Layer:
Logging Interfaces
Other Common Infrastructure components:
Superset FrontendThe frontend of Superset is a sophisticated web client built using modern web technologies to facilitate interactive data visualization. Core Technologies:
Functionality:
|
Github needs the "face melt" emoji as a reaction. Is it possible to "land and expand" here? My trust issues with GPT aside (did it really say "Pytjhon?") I wonder if we can merge a first iteration, then divide/expand/remove/elaborate as needed from there, rather than go deep here. We can feed it to GPT as we go for consolidation/clarification/organization. |
I did a fair amount of prompt-inputs and edits to get to that, but main thing is the structure of the docs (backend/frontend) and mentioning technologies used (and technology choices) in different areas |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can circle back and make this list link to the descriptions of each component below, but let's just merge this thing and dial it in from there.
From here, we can update the installation page to provide a little table (or similar) about how (or if) each installation method installs these components. |
Co-authored-by: Evan Rusackas <evan@preset.io>
SUMMARY